Benedikt Franke
Benedikt Franke
@henzeb that would be great. Let me know if you require further clarification for what needs to be done, I hope the issue description is clear enough.
Using multiple guards is supported somewhat badly. Could you set up a PR with a failing test case as the basis for implementing a fix?
@azz can you take a look? I think this change would benefit many users.
@azz If you no longer want to support this package, that is completely fine. A deprecation notice and archival of the project would be nice in that case, so that...
I created a pull request to fix this: https://github.com/react-component/picker/pull/289
I thought about a generalized solution, but in this case it is not worth it. Creating this pull request took me a few minutes of (admittedly tedious) work, but saved...
For anyone having this same issue, I can recommend `omit-deep-lodash`. It does not mutate inputs, as evidenced by https://github.com/odynvolk/omit-deep-lodash/pull/16
After using this for a while, i found the use of `setTransaction` to be a complete semantic mismatch. I am using routes as transactions for now and turned it off....
Open for suggestions or pull requests to fix this, I do not plan to work on this myself.
Open for improvements to the API or the docs.