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
While you can technically use actions this way already, each one emits a signal event and triggers a reactive UI update on components that use the object data.
With getter methods, the data would remain immutable and simply provide a useful way to bind data manipulations to the store() itself.
Of course, this same thing can be handled today with helper methods as well...
Is it worth having getter methods on the
store()
object that can be used to get and modify data without triggering a signal event?While you can technically use actions this way already, each one emits a
signal
event and triggers a reactive UI update oncomponents
that use the object data.With getter methods, the data would remain immutable and simply provide a useful way to bind data manipulations to the
store()
itself.Of course, this same thing can be handled today with helper methods as well...
As a result, I'm not sure getter methods add all that much value, but they DO increase the complexity of the project.
The text was updated successfully, but these errors were encountered: