Configure prettier arrowParens to match our eslint rules #4876
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.
Impact: minor
Type: chore
Issue
There's one small discrepancy between our defined eslint rules and our (default, it seems) prettier config. eslint wants arrow function arguments always wrapped in parentheses, whereas prettier omits them for single-argument arrow functions.
What this means is if you autoformat your source code with prettier, sometimes it will fail eslint due to this discrepancy.
Solution
Add prettier config to package.json to always wrap arrow function arguments in parens.
Breaking changes
None
Testing
Mostly N/A as this is a tooling issue, but if we start seeing lint errors after running prettier, let me know.