Avoid type widening with enum-typed values in FormValue #541
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.
The current generic type for
FormValue
is this:In this, if you have an enum or constant string type, then it will get widened into a
string
type. TurningDate
andnull
types into string | undefined makes sense, but it is kind of just inconvenient to lose type information if you have an enum.This tweaks the generic type so that if you have a type that
extends string
, then theFormValue
generic uses that type instead of widening to string.