Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
yes, the depth of the object was being counted and there was a place where the if the depth was > 128 it'd throw an error I can't cry about another package having undocumented features that can be annoying or even exploited when I'm doing the same The options were to either update the README or remove the feature (I chose to remove the feature) Because the feature makes it a hassle for anyone who wants to share even a slightly mutable object worrying about preventing the max depth from being reached That said, if you are sharing a slightly mutable object, it is recommended to be VERY specific about what client edits are allowed The next updates should just be documentation updates to show proper code snippets and examples (tests.js is probably confusing right now)
- Loading branch information