What is best practice to initialise a NotifierProvider with a parameter from a widget

[aidanmack]

Im working with some legacy code which does not entirely use riverpod and so I need to initialise my NotifierProvider when the widget starts watching it.

  Widget build(BuildContext context, WidgetRef ref) {


    final state = ref.watch(cardServicesProvider);
    ref.read(cardServicesProvider.notifier).buildCardServicesForQuickView(cardId);

I get these suggestions:

For example, maybe you could update your provider inside a button's
onPressed instead

and

Future(() {...})

Is using a future the only way I can do thi?

I've also seen work arounds making the widget stateful and using

@OverRide
void initState() {
super.initState();
//PostFrameCallback((_)
}

[snapsl]

I would suggest using a family provider to pass the card id.

final state = ref.watch(cardServicesProvider(cardId));

[aidanmack]

Yeah I thought that and and in this context I think I might.
But I'm always a bit on the fence about using family as if further into development something else wants to "watch" changes on that provider, it has to supply the parameter. Sometimes you just want to watch a families providers current state with out initialising it with parameter. Ive never seen a solution to that.