Tweak wording when talking about props changing #5176
Merged
Conversation
This file contains 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
|
Ping @zpao |
|
It wasn't abandoned but accidentally closed. But that's fine. |
zpao
added a commit
that referenced
this pull request
Oct 15, 2015
Tweak wording when talking about props changing
zpao
added a commit
that referenced
this pull request
Oct 19, 2015
Tweak wording when talking about props changing (cherry picked from commit ed7ab7b)
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.
PR abandoned, so I'm commandeering #4366 to tweak wording when talking about props changing. This has come up a couple times recently (#3944, #4122) so I'm using some wording that hopefully is less confusing.