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
I am nut sure if this is a bug, or if there is a way around, but it is a challenge anyway.
I have a mutation that takes no payload. (It just clears a list.)
It looks like this doesn't work properly in an actionGroup.
I think the problem is that there is no payload to add the actionGroup in, and at the moment I am not able to add an empty object as payload.
As a workaround I add a dummy payload, but it would be nice to have a better way.
Also, in the documentation it is referred to test/test-action-group-undo.js. This file does not exist.
The text was updated successfully, but these errors were encountered:
Hi @ottopaulsen, thanks for your feedback and query about this issue.
Based on your user experience, I would have to agree that this isn't the optimal behaviour for the actionGroup feature and that payload should have some default value if a mutation does not require any.
I will also look into correcting the unit test reference: it should be tests/unit/test.action-group.spec.ts.
I am nut sure if this is a bug, or if there is a way around, but it is a challenge anyway.
I have a mutation that takes no payload. (It just clears a list.)
It looks like this doesn't work properly in an actionGroup.
I think the problem is that there is no payload to add the actionGroup in, and at the moment I am not able to add an empty object as payload.
As a workaround I add a dummy payload, but it would be nice to have a better way.
Also, in the documentation it is referred to
test/test-action-group-undo.js
. This file does not exist.The text was updated successfully, but these errors were encountered: