-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
docs(eslint-plugin): add warning about superfluous rules with typescript #7372
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
Conversation
…v6.md Co-authored-by: Josh Goldberg ✨ <git@joshuakgoldberg.com>
…v6.md Co-authored-by: Josh Goldberg ✨ <git@joshuakgoldberg.com>
Thanks for the PR, @Zamiell! 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.
LGTM (thanks!), but will wait for other input since maybe we'd want to automate this a bit more?
Co-authored-by: Brad Zacher <brad.zacher@gmail.com>
Co-authored-by: Brad Zacher <brad.zacher@gmail.com>
I haven't heard back from @Josh-Cena in 2 weeks, so I'll disregard his comment and try using a JSX component. |
Ok, things are looking good now with an MDX component. I also performed a short audit of the rules and found that the warning message also needed to be added to the This PR is now ready for review again. |
Oh sorry, I didn't realize there are things pending on my feedback. FYI @Zamiell MDX partials also support taking props: https://docusaurus.io/docs/markdown-features/react#importing-markdown It should be as easy as taking your component's returned JSX element and converting it to Markdown. I don't have much objection to the current approach, though. |
Looks like the "CI / Website tests (pull_request)" is failing, but I don't think it has anything to do with my PR, correct me if I am wrong. |
It's been 3 weeks and I haven't heard anything from anyone on the team, so pinging Josh/Brad. |
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.
✨ super, thanks!
I like this usage of mdx 😄
PR Checklist
Overview
Adding warning to docs. We probably want to turn this into a template instead, but not sure how to go about that right now.