-
Notifications
You must be signed in to change notification settings - Fork 37
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
Support application "packs" #67
Comments
I think there are couple of concerns to address. 1- What could be the file structure to ease community proposal of "packs"
|
@danielpetisme thanks for the feedback!
I believe it could be the same in PR #69 Packs would define a set of dependencies, perhaps force a language, and sometimes require build plugins configuration. But we'll keep generating empty verticles and test. We don't want to create a code generator. Just create the project base. Then users can go to the guides to copy/past code :)
Packs would be static.
I expect most packs to tolerate any language. But we could force a language in some cases.
No we shouldn't. The goal is not to create a code generator, but simply to relieve users from the initial setup effort. |
Currently, the starter lets you select dependencies for the project. This is fine for most projects, but some scenarios require more setup. As a start, we could have packs for an application with:
For such cases, we could have a "pack" input (similar to dependencies) which would generate everything needed.
The text was updated successfully, but these errors were encountered: