-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): consistent .mdx file naming #6325
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
chore(website): consistent .mdx file naming #6325
Conversation
Thanks for the PR, @JoshuaKGoldberg! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
src="https://img.shields.io/npm/v/@typescript-eslint/parser/canary.svg?style=flat-square" | ||
alt="NPM Version" | ||
/> | ||
</a> |
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.
🤷 I guess Prettier more aggressively formats inline HTML snippets in .mdx
files than .md
.
PSA: |
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.
fix conflicts and |
Overview
Spinning off from #6318:
Upper_Snake_Case.mdx
.md
anywayCONTRIBUTING.md
to https://typescript-eslint.io/contributing