-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(website): pass user defined compilerOptions to linter #5080
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
Thanks for the PR, @armano2! 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. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
sadly no, we can't really define defaults, user is not going to be able to disable them for now, changing defaults requires changes to be done in config editor, but that will be done when i get to improving config editor Config editor currently removes all options that are set to false (yes this is bad, but that's how it was done) added to backlog, Website Playground (view) |
PR Checklist
Overview
compilerOptions
to be passed to WebLinterTest cases