-
Notifications
You must be signed in to change notification settings - Fork 638
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
🏛 fix: quiet logs when linting in CI #4070
Merged
estrattonbailey
merged 1 commit into
develop
from
eric/rnbw-4371-use---quiet-option-when-linting-in-ci
Sep 2, 2022
Merged
🏛 fix: quiet logs when linting in CI #4070
estrattonbailey
merged 1 commit into
develop
from
eric/rnbw-4371-use---quiet-option-when-linting-in-ci
Sep 2, 2022
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
RNBW-4331 Use recommended ESLint settings
At the moment we've manually configured ESLint rules (almost 400 lines worth) and ignored the recommended settings. This is swallowing a handful of errors that really should not be ignored, like:
Based on my tinkering, we can improve this situation fairly quickly. |
Base automatically changed from
eric/rnbw-4331-use-recommended-eslint-settings
to
develop
August 25, 2022 18:23
estrattonbailey
requested review from
estebanmino,
osdnk and
markdalgleish
as code owners
August 25, 2022 18:23
estrattonbailey
force-pushed
the
eric/rnbw-4371-use---quiet-option-when-linting-in-ci
branch
from
August 25, 2022 18:51
5c59d7b
to
4d39d05
Compare
estrattonbailey
changed the title
fix: quiet logs when linting in CI
🏛 fix: quiet logs when linting in CI
Aug 25, 2022
7 tasks
estebanmino
approved these changes
Sep 2, 2022
skylarbarrera
approved these changes
Sep 2, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🏛️
estrattonbailey
deleted the
eric/rnbw-4371-use---quiet-option-when-linting-in-ci
branch
September 2, 2022 20:06
estrattonbailey
added a commit
that referenced
this pull request
Sep 6, 2022
…w-4378-clean-up-global-and-env-vars-in-app-move * 'develop' of github.com:rainbow-me/rainbow: (40 commits) fix: quiet logs when linting in CI (#4070) analytics: add tracking for screen dimensions + fix nav events on android (#4088) fix native input cursor color (#4112) Profiles: use `name` text record instead of `me.rainbow.displayName` (#4046) chore: upgrade eslint-config-rainbow (#4118) backup PIN (#4012) Remove long press on address in switching wallets (#3990) Version bump iOS v.1.7.4 & Android 144 (#4117) Fix slow image loading (#4052) Add new text size scale, deprecate old sizes and Heading (#4113) Disable campaings in e2e and fix testID of PromoSheet (#4107) 🏛 chore: prettier everything (#4100) fix settings StatusIcon shadows on android (#4104) fix clear async storage crash (#4105) fix RNBW-4416 (#4103) 🏛 Update to React Query 4 (#4060) swaps: init cross chain feature flag (#4091) enable arbiitrum swap details test (#4092) remove unsafe access to networkInfo (#4096) network check (#4094) ...
estrattonbailey
added a commit
that referenced
this pull request
Sep 6, 2022
…w-4388-configure-jest-for-unit-tests * 'develop' of github.com:rainbow-me/rainbow: Profiles: Support contenthash (#4067) 🏛 GraphQL Clients/Codegen Foundations (#4086) fix: quiet logs when linting in CI (#4070) analytics: add tracking for screen dimensions + fix nav events on android (#4088) fix native input cursor color (#4112) Profiles: use `name` text record instead of `me.rainbow.displayName` (#4046) chore: upgrade eslint-config-rainbow (#4118) backup PIN (#4012) Remove long press on address in switching wallets (#3990) Version bump iOS v.1.7.4 & Android 144 (#4117) Fix slow image loading (#4052) Add new text size scale, deprecate old sizes and Heading (#4113)
estebanmino
pushed a commit
that referenced
this pull request
Sep 9, 2022
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.
Fixes RNBW-4331
What changed (plus any additional context for devs)
With the new ESLint setup, we have >4k warnings. These only useful when commiting changes locally via the
lint-staged
pre-commit
git hook. In CI, we should only surface errors. This is what the--quiet
option does.Since yarn's handling of passed arguments to npm scripts might not be clear to everyone, I opted to spell out the whole command in the GitHub Action instead of
yarn lint --quiet
.Final checklist
team1/team2
,critical path
,release
,dev QA
)dev QA
label, did you add the PR to the QA Queue?