Is ref.read ok with mundane things in notifier build() functions?

[gazialankus]

Colleagues tend to use ref.read from time to time in build() functions of notifiers and I have the knee jerk reaction that ref.watch is more appropriate. However there are things that I know won't refresh, like a logging service, or permission request service that we obtain through Riverpod. Heck, it could create weird situations if the logging service was ever refreshed, so many logs around causing everything else to refresh... Is it OK to use ref.read for such things?

Should we start classifying which ref.read usages are OK to use in build() functions or enforce the rule that they should all be ref.watch?

[taiju59]

Providers are cached, so ref.watch won't re-fetch if the value hasn't changed. Using ref.watch everywhere seems fine.

[rrousselGit]

Avoid ref.read as much as possible. To begin with, I'll most definitely deprecate this API soon.

[gazialankus]

Sounds like a great plan. It's currently a nuissance that people get fixated on.

[gazialankus]

Does this mean that we can use ref.watch everywhere today?