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

[eslint] merge eslint and eslint_with_types CLIs #117934

Open
spalger opened this issue Nov 8, 2021 · 2 comments
Open

[eslint] merge eslint and eslint_with_types CLIs #117934

spalger opened this issue Nov 8, 2021 · 2 comments
Assignees
Labels
impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:large Large Level of Effort Team:Operations Team label for Operations Team

Comments

@spalger
Copy link
Contributor

spalger commented Nov 8, 2021

In #114184 we added node scripts/eslint_with_types to get Type-powered ESLint rules working in the repo. We need to merge this with the standard eslint configs though so that ESLint can run in IDEs with types enabled.

@spalger spalger added the Team:Operations Team label for Operations Team label Nov 8, 2021
@spalger spalger self-assigned this Nov 8, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort labels Feb 16, 2022
@tylersmalley tylersmalley removed loe:small Small Level of Effort impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Mar 16, 2022
@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Mar 17, 2022
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort loe:large Large Level of Effort and removed loe:medium Medium Level of Effort labels Mar 22, 2022
@afharo
Copy link
Member

afharo commented May 1, 2024

Just adding #181456 (comment) as a reason for doing this.

cc @pmuellr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:large Large Level of Effort Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

4 participants