chore(generators): improve generator Typescript types #1439
Conversation
This file contains 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
anshumanv
approved these changes
Apr 11, 2020
jamesgeorge007
approved these changes
Apr 11, 2020
rishabh3112
approved these changes
Apr 11, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
chore/refactor
Did you add tests for your changes?
No
If relevant, did you update the documentation?
No
Summary
There was a lingering TODO in
init-generatorto switch the type ofentryOptiontostring | object. I did this and restricted some other types more as well.Open to suggestions if my exporting of
CustomGeneratorclass from thetypesmodule is not elegant.Does this PR introduce a breaking change?
No
Other information