[No QA] Update propTypes files to use camelCase #6005
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
|
I know we are on a feature freeze atm and avoiding risk, but despite the high file count here I'd argue this is very low risk since no behavior was changed. Going for the merge! |
|
🚀 Deployed to staging by @marcaaron in version: 1.1.8-20 🚀
|
roryabraham
changed the title
|
🚀 Deployed to production by @roryabraham in version: 1.1.10-2 🚀
|
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.
Details
Style change to make all
propTypesmodules usecamelCase.Fixed Issues
$ #6004
Tests / QA Steps
Test app for general regressions. Make sure all things are possible. This is a style change so there is nothing in particular to test.
Tested On