More broadly rename MemberExpressions #199
Merged
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
bvaughn changed the title 
gaearon approved these changes Feb 2, 2018
| Good catch. I’m so glad our names are greppable and not just onMount |
| Oh my goodness, no kidding |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
Follow-up to #198
When running this codemod internally I found several additional places manually invoking lifecycles like
SomeComponent.componentDidMount.apply()so the codemod has been updated to handle this case also.So I've changed the codemod from renaming
CallExpressions (eginstance.method()) to broaderMemberExpressions (eginstance.method()andinstance.method.apply()).Additional tests have been added.