Enable 'strictNullChecks' in tsconfig samples, closes #1299 #1301
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull Request Overview
This PR adds recommendations to enable TypeScript's strictNullChecks compiler option across documentation to improve type inference for ESLint React rules.
- Added
strictNullChecks: trueto TypeScript and JavaScript configuration examples - Added a warning callout explaining that certain rules (like
react-x/no-leaked-conditional-rendering) work better withstrictNullChecksenabled
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| apps/website/content/docs/getting-started/typescript.mdx | Added strictNullChecks option to the tsconfig.json example |
| apps/website/content/docs/getting-started/javascript.mdx | Added strictNullChecks option to the jsconfig.json example |
| apps/website/content/docs/configuration/configure-project-config.mdx | Added warning callout with explanation and example for enabling strictNullChecks |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
apps/website/content/docs/configuration/configure-project-config.mdx
Outdated
Show resolved
Hide resolved
…ig.mdx Co-authored-by: Copilot <[email protected]> Signed-off-by: REL1CX <[email protected]>
This was referenced Nov 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Checklist
fix: remove a typo, closes #___, #___)Other information