Outputs are being mutated when they shouldn't
See original GitHub issueDescribe the bug Output is not remaining normalized
To Reproduce Current settings:
Methods.mutation.MOD_ACTIVATION.mutateOutput = false;
Methods.mutation.SWAP_NODES.mutateOutput = false;
Expected behavior
- Outputs remain normalized when mutateOutput is set to false.
- Default behavior is to keep output normalized
Screenshots
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Should a component commit a mutation directly? #587 - GitHub
Components could directly call mutators, but they shouldn't. They should call only actions. Actions could performing only one mutation, ...
Read more >Why is mutating the [[prototype]] of an object bad for ...
According to this by mutating they mean reassigning. In that case using fred = Object.create(Object.prototype) should be just as bad. But they specifially...
Read more >Why you shouldn't mutate parameters - SeanMcP.com
Mutating parameters. When you pass a variable as an argument, you are handing a reference to the function – not a value. So...
Read more >Discuss Remove the minimum - Codewars
You 've mutated input list (expectation assertion is on value of input list, not output of method): [277, 372, 73, 109, 62, 270,...
Read more >What is a Mutation in GraphQL and how to use it | Aditya's Blog
It is possible that multiple mutations need the same input arguments. So it is a good practise to create Input Types and reuse...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@dan-ryan The tests were running fine on our end now - are you still running into the issue?
Since I can’t run the latest build without crashing while evolving, testing will have to wait.