Using family provider notifier. Is this good or there is a better approach?

[ebsangam]

I need both notifier and state of a Family Provider. Is this okay to do like this or there is a better approach?

Here user is provided as initial value for the form controller.

class UpdateProfilePage extends ConsumerWidget {
  const UpdateProfilePage(this.user, {super.key});

  final User user;

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    final l10n = context.l10n;

    final state = ref.watch(updateProfileControllerProvider(user));
    final notifier = ref.read(updateProfileControllerProvider(user).notifier);

    return Scaffold(
      appBar: AppBar(
        title: Text(l10n.updateProfile),
      ),
    );
  }
}

[ebsangam]

I saw this, so this should not be a good practice. What would be the solution of such case?

Family parameters aren't meant to be "initial properties". It's voluntary as this is what empowers cool reactive stuff.

[ebsangam]

So currently I am doing like this and it is working,

@Riverpod(dependencies: [])
User initialForm(InitialFormRef ref) => throw UnimplementedError();

@Riverpod(dependencies: [initialForm])
class UpdateProfileController extends _$UpdateProfileController {
  @override
  UpdateProfileState build() {
    final user = ref.watch(initialFormProvider);
    return UpdateProfileState(
      form: ProfileForm(
        firstName: user.firstName,
        lastName: user.lastName,
        address: user.address,
        image: user.image,
      ),
    );
  }
}

class UpdateProfilePage extends StatelessWidget {
  const UpdateProfilePage(this.user, {super.key});
  final User user;

  @override
  Widget build(BuildContext context) {
    return ProviderScope(
      child: const UpdateProfileScaffold(),
      overrides: [
        initialFormProvider.overrideWithValue(
          const User(id: 'id', firstName: 'Sangam'),
        ),
      ],
    );
  }
}