Closed rafaeldev closed 10 months ago
Hey hey, I think the problem is that this is a hash at the end of the day, and when you are setting it to either {function1: false}
or {function2: false}
, which makes the other field to be the default (true). You can fix that with .merge
for sure and make things a bit more explicit.
Please let me know if it does not help and reopen the issue 🙂
I have an update context for user preferences which can be changed on differents pages:
Controller A
StoreModel
When I call ControllerA passing
function1
to befalse
and after calling ControllerB passingfunction2
to befalse
,function1
is updated totrue
.I think so can I skip that working with
#merge
method... I need to know if it is a bad pattern on my side or if there is another alternative for this scenario