Improve description of AllowUpdates - #37494
Open
guardrex wants to merge 3 commits into
Open
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.
Fixes #37483
Ilona ... I opened a framework API summary change for this at dotnet/aspnetcore#68618. I need help interpreting and selecting the best language for Dan's remark over here ...
I'd like to specify that we're talking about property mutations and not use the word "later" unless we end up specifying when "later" is, so my draft goes like this ...
For >=11.0 ...
For >=10 and <11.0 ...
We could also work further with the word "control" as well. Should it state something more like ...
If correct, such a change clarifies what "control" means in the original sentence.
Internal previews