fix: mistake in allowArrowFunction #3054
Closed
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
|
See my comment here: #2255 (comment) In other words, arrow functions are fine in an HTML element, and in a custom component, are only a problem if the custom component isn't just stamping them onto an HTML element. |
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.
What does this PR do?
This PR fixes the incorrection in allowArrowFuntion "true" to "false" in react.js.
Fixes #2255
##Type of change
Bug fix (non-breaking change which fixes an issues).
##How should this be tested?
-[]Go to react.js file
-[]Check the line no 112 that bug in allowArrowFunction "false"
##Mandatory Tasks
-[X] Make sure you have self-reviewed the code.A decent size PR without self-review might be rejected.