feat: add templatesDir option to getTemplateFile #292
Merged
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.
Description
If you're using the generator as a library, your application's
node_modules
will be different than the defaultDEFAULT_TEMPLATES_DIR
. For instance:If I use the generator as a library in this scenario,
DEFAULT_TEMPLATES_DIR
would bemy-app/node_modules/@asyncapi/generator/
and using the@asyncapi/html-template
would result in the template being installed as a sibling of the generator, like above. Therefore, usinggetTemplateFile('@asyncapi/html', 'partials/content.html')
will result in an attempt to access the filemy-app/node_modules/@asyncapi/generator/node_modules/@asyncapi/html-template/partials/content.html
, which is incorrect.This PR lets you change the
DEFAULT_TEMPLATES_DIR
only for thegetTemplateFile
method.