Skip to content
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
merged 1 commit into from
Jul 2, 2020

Conversation

oliviertassinari
Copy link
Member

@oliviertassinari oliviertassinari commented Jun 13, 2020

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

package.json Outdated Show resolved Hide resolved
@oliviertassinari oliviertassinari added the on hold There is a blocker, we need to wait label Jun 25, 2020
@oliviertassinari
Copy link
Member Author

oliviertassinari commented Jun 25, 2020

@dtassone Question, do you still want to get the lint command in each package's scripts?

@oliviertassinari 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 oliviertassinari force-pushed the sync-eslint-with-main-repository branch 4 times, most recently from 6dbc9cd to 58cb97a Compare June 28, 2020 18:08
@oliviertassinari 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
@oliviertassinari oliviertassinari added the core Infrastructure work going on behind the scenes label Jun 28, 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",
Copy link
Member

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?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

package.json Outdated Show resolved Hide resolved
packages/panel/package.json Outdated Show resolved Hide resolved
@oliviertassinari oliviertassinari force-pushed the sync-eslint-with-main-repository branch 2 times, most recently from 3e2a417 to 13d0ad9 Compare July 1, 2020 22:14
@oliviertassinari oliviertassinari requested a review from dtassone July 1, 2020 22:32
@oliviertassinari oliviertassinari force-pushed the sync-eslint-with-main-repository branch from e9d0101 to 0273bfc Compare July 2, 2020 09:00
@oliviertassinari oliviertassinari merged commit 59d5336 into master Jul 2, 2020
@oliviertassinari oliviertassinari deleted the sync-eslint-with-main-repository branch July 2, 2020 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Infrastructure work going on behind the scenes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants