-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[core] Align the eslint configuration with the main repository #23
Merged
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
1 task
dtassone
reviewed
Jun 25, 2020
@dtassone Question, do you still want to get the lint command in each package's scripts? |
oliviertassinari
added
PR: needs revision
The pull request can't be merged. More details is available on the code review or fails in the CI
and removed
on hold
There is a blocker, we need to wait
labels
Jun 25, 2020
oliviertassinari
force-pushed
the
sync-eslint-with-main-repository
branch
4 times, most recently
from
June 28, 2020 18:08
6dbc9cd
to
58cb97a
Compare
oliviertassinari
removed
the
PR: needs revision
The pull request can't be merged. More details is available on the code review or fails in the CI
label
Jun 28, 2020
dtassone
approved these changes
Jul 1, 2020
package.json
Outdated
@@ -19,10 +19,16 @@ | |||
"@types/styled-components": "^5.0.1", | |||
"@typescript-eslint/eslint-plugin": "^2.19.0", | |||
"@typescript-eslint/parser": "^2.19.0", | |||
"babel-eslint": "^10.1.0", |
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.
why do we need all this extra pkgs?
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.
oliviertassinari
force-pushed
the
sync-eslint-with-main-repository
branch
2 times, most recently
from
July 1, 2020 22:14
3e2a417
to
13d0ad9
Compare
oliviertassinari
force-pushed
the
sync-eslint-with-main-repository
branch
from
July 2, 2020 09:00
e9d0101
to
0273bfc
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.
A step that will help with alignment with the main repository: #6. The end goal is: one single configuration for all the infrastructure tooling, low entropy, high consistency. I start with eslint because as one of the highest ROI tasks on this matter.
Regarding Lodash, we might want to ignore the prettier update coming from it, until we remove it from the source: #7