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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code Cleanup: Enforce Linting Rules & Update UNSAFE_ React Lifecycle Events #559
Code Cleanup: Enforce Linting Rules & Update UNSAFE_ React Lifecycle Events #559
Changes from 1 commit
75b00918d370823049bd1fe03ad7f11bc185f3471ed4d84dc17f90eda77cd1bc31dbaf3d50aff227d0120988a29b55be21241747ceb413fbac0ec93fd954ebe815546ae8ffcc4c56460c5ef6633ca24024533fd7590aa60ecb62e8f634c1dea5143275a88cb68493d262970629b4d16c2cb47a1File filter
Jump to
finish linting errors for no-restricted-syntax. 1 remains: couldn't r…
christophertinoJun 4, 2020
Member
Remove 'no-restricted-syntax'
IAmThePanJun 11, 2020
Author
Contributor
updated in feature/cleanup-cleanup as this PR was already merged.
wlycdgrJun 11, 2020
Member
lgtm in feature/cleanup-cleanup
wlycdgrJun 11, 2020
Member
We could get rid of the loop altogether, no?
IAmThePanJun 12, 2020
Author
Contributor
Much more elegant. Updated on
feature/cleanup-cleanup.wlycdgrJun 15, 2020
Member
lgtm on feature/cleanup-cleanup
wlycdgrJun 11, 2020
Member
As above, how come we are not using
forEachhere? Or is some Airbnb rule other than 11.1 (which suggests this) behind this change?IAmThePanJun 12, 2020
•
edited
Author
Contributor
I can't update this loop to
forEachbecause you can't break out of aforEachand return without doing something unnatural with errors. I could do.somebut it's not as readable. Keeping as is for now.wlycdgrJun 11, 2020
Member
Same
forEachquestionIAmThePanJun 12, 2020
Author
Contributor
Same as above. This loop uses a
breakwhich you can't elegantly cause with aforEachloop. Keeping it as is for now.wlycdgrJun 11, 2020
Member
And here
IAmThePanJun 12, 2020
Author
Contributor
Same reasoning as above.
wlycdgrJun 11, 2020
Member
Same question re:
forEach. I won't mention it again so as not to clutter up the PR more - if it does make sense to change the other instances should be easy to find.IAmThePanJun 12, 2020
Author
Contributor
Same as the others. I didn't update this one because the loop uses a continue.