-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Adding documentation for watch and proxied objects #734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@bencodezen told me to tag him in this as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fimion thank you for working on this! I've added a few comments to the PR
7c37314
to
9dc8dd1
Compare
Co-authored-by: Natalia Tepluhina <[email protected]>
9dc8dd1
to
6abcf91
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fimion thank you for all the changes! I've added a few more points to review
Co-authored-by: Natalia Tepluhina <[email protected]>
Co-authored-by: Natalia Tepluhina <[email protected]>
Co-authored-by: Natalia Tepluhina <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work on this @fimion and @NataliaTepluhina for the great reviews!
I think we're good to go for release so people can utilize this information. We can always iterate in another PR!
Description of Problem
The way a developer needs to use watch on a proxied object is not well documented. I have outlined more details in #733
Proposed Solution
Add details about shallow copying and deep copying an object to see both the old and new values of it.
Additional Information