feat: new argument to use a custom external generator #311
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
dunglas
approved these changes
Nov 16, 2021
Shywim
force-pushed
the
feature/support-custom-templates
branch
from
b47ae30 to
ab90a62
Compare
actually add the command don't use a new argument
Shywim
force-pushed
the
feature/support-custom-templates
branch
from
ab90a62 to
b744312
Compare
dunglas
approved these changes
Nov 16, 2021
|
Thank you! |
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.
This allow the
-g/--generatorargument to specify a path, allowing to use custom generators.The argument can point to any node module.
A quick and dirty command to test is available as
yarn test-gen-custom.Notes:
asyncfunction because we do a dynamic import to load the custom generator insidesrc/generators.jsTODO: