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
Just thought I'd throw this out there (was think of making an addon) and see if this belongs here:
A component, something like:
{{#state-group'stateName'identifier=modelas |state|}}<!-- use state here -->{{/state-group}}<!-- or buffered -->{{#state-group'stateName'identifier=modelbuffered=trueonapply=(route-action'saved')
as |stateactions|}}<!-- use state here -->
<buttononclick={{actionactions.apply}}>Save</button>
<buttononclick={{actionactions.reset}}>Reset</button>
{{/state-group}}
Basically every time this renders you would have like a persistent state object that can be modified without having to inject or make a CP.
The text was updated successfully, but these errors were encountered:
I'm unsure if a single special purpose component makes sense, or using state-services in custom components that accomplish this make sense.
Although I like where this is going, It would be fun to play with this (for now) as a second add-on, as I feel we have more research todo (as you mentioned \w "idea" prefix)
Just thought I'd throw this out there (was think of making an addon) and see if this belongs here:
A component, something like:
Basically every time this renders you would have like a persistent state object that can be modified without having to inject or make a CP.
The text was updated successfully, but these errors were encountered: