Mention unwrapping of refs for readonly and shallow proxies #840
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is something that came out of a conversation on Discord.
The API reference for
reactivealready mentions that anyrefproperties will be automatically wrapped/unwrapped.I've added a similar note to
readonly. It's a simpler cases because the value can't be changed via a readonly proxy.I've also added notes to
shallowReactiveandshallowReadonly. They don't have automatic unwrapping ofref, which came as a surprise to me. From looking at the source code it does appear to be a deliberate design decision for them to work that way.