You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Ref is short for reference? Or?
Describe the solution you'd like
Call it Pod because it is a pod of content and it fits perfectly with Riverpod from an aesthetic and branding point of view. A Pod is a container of content/state.
Describe alternatives you've considered
Keep using Ref
Additional context
Kinda like Bloc has Blocs and Cubits, and Signals have Signals, Riverpod could have Pods. To me it's so obvious and would just bring everything together because Pod is actually descriptive, yet short.
Looking at the code even as a first timer you would assume Pod pod WidgetPod are part of Riverpod without even thinking about it.
Also WidgetPod makes sense too.
The text was updated successfully, but these errors were encountered:
yeah i understand, not such a fan of breaking changes myself but might be a neat alternative name for RP3. and legacy naming Ref could still work throughout the life of Riverpod in subsequent versions
Is your feature request related to a problem? Please describe.
Ref is short for reference? Or?
Describe the solution you'd like
Call it Pod because it is a pod of content and it fits perfectly with Riverpod from an aesthetic and branding point of view. A Pod is a container of content/state.
Describe alternatives you've considered
Keep using Ref
Additional context
Kinda like Bloc has Blocs and Cubits, and Signals have Signals, Riverpod could have Pods. To me it's so obvious and would just bring everything together because Pod is actually descriptive, yet short.
Looking at the code even as a first timer you would assume Pod pod WidgetPod are part of Riverpod without even thinking about it.
Also WidgetPod makes sense too.
The text was updated successfully, but these errors were encountered: