Add support for exactOptionalPropertyTypes
TypeScript option
#77
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.
TypeScript 4.4 introduced
exactOptionalPropertyTypes
compiler option. This fixed one of the major issues I had with TypeScript and, I think, should be the default in all new projects. It avoids unnecessary checks and type assertions/casts, improving type safety. But it also means that all optional object field types in the project, including those from third-party libraries, have to explicitly includeundefined
to preserve the old behavior.This PR is mostly just convenience, so I could do
instead of
This PR:
undefined
to optional object field types where applicable (which is most of them).exactOptionalPropertyTypes: true
to TypeScript configuration.tsconfig.json
because it's weird to add options with the boilerplate in the way.While I'm at it, would that be ok to do some maintenance tasks too? Like: