[code-infra] Create custom rule for undefined in optional props #909
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.
This rule naively (currently) checks for all optional properties in interface and types and provides autofix to add
| undefinedwherever it doesn't exist.One optimization is added where locally defined types are also checked for
| undefinedand if it already hasundefined, its not added at places where the type is used.See tests for scenarios. We can optimize the discovery further by allowing options to, for example, only affect optional properties of exported types/interface.
Integration PR in Base UI - mui/base-ui#3302