[chore] Update lint and config to be more consistent with other expo codebases #308
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
|
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @wschurman and the rest of your teammates on |
wschurman
force-pushed
the
@wschurman/09-19-_chore_update_lint_and_config_to_be_more_consistent_with_other_expo_codebases
branch
from
424098f
to
ba9ed07
Compare
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.
Additional context
An indentation nit was raised in a previous PR: https://app.graphite.dev/github/pr/expo/expo-github-action/306/continuous-deploy-fingeprint-Output-whether-each-platform-build-was-created-or-one-was-reused#comment-PRRC_kwDOCaaLa85pRAUA
Lint should take care of this to reduce review responsibility. This updates prettier settings for that particular issue, but also updates lint to be more aligned with other node repos in the expo org.