-
-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce remote-templates support #235
Comments
Is anyone already working on this? |
Not yet but it's top priority right now so we should start working on it probably next week. |
How will you solve the core and template dependency alignment issue? We initially just pulled the tpls in via git but then when the core brought in new features or a new format the older tpls started to break so we went with a quick and dirty solution of tagging the tpl git branches then comparing again the core npm version: https://github.com/acrontum/openapi-nodegen/blob/master/src/lib/template/TemplateFetch.ts#L183 We were just speaking the other day internally about changing this as confused a few of our team mates and to instead use the built in versioning system from NPM opposed to git tagging. It is a tricky one to solve and be clear to the end user. Scenario being: |
Nice! Looking forward to it 👍 |
Implemented in #261 |
Thanks, man! 👍 |
Reason:
To simplify development of the templates, and also usage of templates we want to make it possible to publish templates separately and then have an option to use them in a generator from a remote location.
Description:
The text was updated successfully, but these errors were encountered: