docs: mention strict configs' stricter default rule options #8719
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. |
| `const defaultOptionsRecommended: Options = ${defaults};`, | ||
| '', | ||
| '// These options are merged on top of the recommended defaults', | ||
| `const defaultOptionsStrict: Options = ${JSON.stringify(recommended.strict)};`, |
There was a problem hiding this comment.
I'd have liked to apply the actual merging logic so folks can see what the true defaults are for strict. But that'll be a little more involved. In the interest of getting this done faster I'd rather just merge this PR ASAP. Thoughts?
There was a problem hiding this comment.
I think this is good for quick fix. I'd like to see the merged config. Tho on second hand, it’s nice to see easily what are the things that changed.
So maybe this needs more thought with time? But for now this looks good to me. 👍
PR Checklist
Overview
Mentions the differences in configs in two ways:
defaultOptions*variables