Allow caller to customize type parsing behavior #3
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
justjake
force-pushed
the
jake--known-types-2-less-generics
branch
from
49b3a7c to
5a84291
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR adds a new SimpleType,
SimpleTypeCustom. The custom type can contain arbitrary data, typed as unknown for now. The ts-simple-type will never produce this type by default.Then, we allow the caller to extend the to-simple-type parser with a new optional callback argument:
toCustomType.toCustomTypecan either implement its ownts.Type->SimpleTypeconversion, or it can return a "wrapper" function that will be called withts-simple-type's default conversion of thatts.Type.TODOs
liftGenericcall pattern or implementation. This needs to be investigated.