-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): fix base rule source links for extended rules #6294
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): fix base rule source links for extended rules #6294
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. |
PR Checklist
Overview
If
meta.docs.extendsBaseRule
istrue
, then we should just go withfile.stem
.Corrects the link to be the right md source path. Also moves the link to be underneath the new Resources section while I'm in the area. Feels like that makes more sense.