-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs: reference eslint-stylistic around formatting docs #7733
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
docs: reference eslint-stylistic around formatting docs #7733
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 configuration. |
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.
Looks great! Thanks a lot for the support! (and working on it so quickly!) 💚
PR Checklist
Overview
Applies a few touchups to the What About Formatting? page:
Also changes the auto-generated admonition on top of formatting rules to point to eslint.style.
cc @antfu - if you have the time, I'd greatly appreciate your review on this. Is this wording accurate and not too harsh still? Is there more reasoning you'd want to add for using eslint.style instead of a dedicated formatter? Is there anywhere else you think we should add something?