fix(): do not remove undefined from ConfigService.get return type #1304
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The return type of a validated
ConfigService.get
excludesundefined
. This hides null errors in the following case.Issue Number: #1302
What is the new behavior?
The return type now no longer excludes undefined if
WasValidated
is true.Does this PR introduce a breaking change?
Users that have strictNullChecks enabled, have optional properties on their Env class, and depend on the behavior of
ConfigService.get
strippingundefined
from the return type will receive type errors. Example of code that would now result in errors:The TypeScript error raised:
I would argue that their types are wrong and this is exposed by this PR.