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

Ask which languages to lint #148

Open
nzakas opened this issue Oct 3, 2024 · 0 comments · May be fixed by #151
Open

Ask which languages to lint #148

nzakas opened this issue Oct 3, 2024 · 0 comments · May be fixed by #151
Assignees
Labels

Comments

@nzakas
Copy link
Member

nzakas commented Oct 3, 2024

Now that we can lint JSON and Markdown, we should incorporate this into the setup flow.

First Question

The first question should now be (with checkboxes):

What do you want to lint?
(x) JavaScript
( ) JSON
( ) JSON with comments
( ) JSON5
( ) Markdown

The JavaScript option should be checked by default and if unchecked, we should add this to the config:

{
    ignores: ["**/*.js", "**/*.cjs", "**/*.mjs"]
}

If Markdown is Checked

If someone checks Markdown, then we should ask (radio buttons):

What flavor of Markdown to you want to lint?
(x) CommonMark
( ) GitHub-Flavored Markdown
@eslintbot eslintbot added this to Triage Oct 3, 2024
@github-project-automation github-project-automation bot moved this to Needs Triage in Triage Oct 3, 2024
@aladdin-add aladdin-add moved this from Needs Triage to Ready to Implement in Triage Oct 10, 2024
@aladdin-add aladdin-add self-assigned this Oct 10, 2024
aladdin-add added a commit that referenced this issue Oct 25, 2024
aladdin-add added a commit that referenced this issue Nov 4, 2024
@aladdin-add aladdin-add linked a pull request Nov 4, 2024 that will close this issue
@aladdin-add aladdin-add moved this from Ready to Implement to Implementing in Triage Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Implementing
Development

Successfully merging a pull request may close this issue.

2 participants