-
Notifications
You must be signed in to change notification settings - Fork 50
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
[Feature]: eslint markdown, json #1295
Comments
People can be co-author:
|
I believe applying @eslint/markdown could help us write code blocks more consistently. Would it be okay if I take a look into this? |
Sure! |
1 task
manudeli
added a commit
that referenced
this issue
Oct 12, 2024
# Overview <!-- A clear and concise description of what this pr is about. --> related to #1295 I have implemented ESLint linting for MDX files in this project. ### Changes - Integrate `eslint-plugin-mdx` to enable linting for MDX files - Apply Prettier rules and JavaScript rules to code blocks within MDX files - Update existing MDX files to comply with the new linting rules This enhancement will improve code consistency and readability across our MDX documentation. ### Additional Notes - While [mdx/remark rules](https://github.com/mdx-js/eslint-mdx?tab=readme-ov-file#rules) offer potential for more diverse rule sets, they are not implemented in this PR. This could be explored in future iterations. - `@eslint/markdown` is designed for `md` files. Since the majority of Suspensive's documentation uses `MDX`, linting for md files was not considered in this implementation. ## PR Checklist - [x] I did below actions if need 1. I read the [Contributing Guide](https://github.com/toss/suspensive/blob/main/CONTRIBUTING.md) 2. I added documents and tests. --------- Co-authored-by: Jonghyeon Ko <[email protected]> Co-authored-by: 김석진(poki) <[email protected]> Co-authored-by: Gwansik Kim <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Package Scope
etc
Description
Lint!
Possible Solution
No response
etc.
No response
The text was updated successfully, but these errors were encountered: