fix(proxy-observation): prevent proxies from being wrapped in proxies again #1716
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
📖 Description
If you pass in a property that's part of a computed observation structure into another class, the value is already wrapped in a proxy before that property is observed in the new class. If that new class then also uses computed observation, that property will be wrapped in a proxy again, causing a "proxy within a proxy". This can repeat itself endlessly, causing all sorts of issues.
Simply adding the proxy itself as the key to the
proxyMap
will solve that problem at least as far as the issue in our app is concerned.cc @bigopon
🎫 Issues
👩💻 Reviewer Notes
📑 Test Plan
⏭ Next Steps