💡 Proposing to club generic wrappid templates with toolkit #6
Closed
anantakumarghosh
started this conversation in
Ideas
Replies: 2 comments 2 replies
-
|
I am not sure how that will help |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Closing this discussion as not valid on today's date. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @wrappid/core-team 🙌
I have an interesting idea
What if we club generic wrappid templates(app, module, service) with toolkit?
(generic term refers to initial wrappid templates: wrappid-app, wrappid-module, wrappid-service)
Current Behavior:
Toolkit copies wrappid template into org/user's repository
Proposing:
Wrappid templates will be inside toolkit package, templates will be cloned/pulled before build-publish process
If there are some more template variation(not generic) or custom app template, like a wrappid-app that looks completely different,
for example let us assume it as a template named: wrappid-lightApp
Toolkit won't have it. Instead users will have to download and import custom template in toolkit with some command like,
wrappid template add [path of template].Feel free to share your thoughts, pros and cons 😄
Beta Was this translation helpful? Give feedback.
All reactions