-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
CLI version of jhlite #11793
Comments
There is already a try on this, I don't remember the project name. |
The approach was different, focusing on customizing mustache templates. Reading the issue, the idea was to create a new project for that. Can the command I suggested be implemented in this project at infrastructure/primary? WDYT? |
This is something I had in mind, but I have never found the time to work on. If we should implement it, I think it should be a separate repository / maven artifact, and that we should also handle the loading custom modules from custom jhlite. |
I am really interested in this cli option. I read the project code: It is really well done, i am thinking of using it to integrate into jhipster-lite as a separate maven artifact 😀 I am going to look at your project too, @murdos ! Edit: into jhipster-lite as a separate maven module |
I've never thought about that before this comment.
My suggestion for the first version is a single command that only applies the module:
jhlite apply <module-slug-name>
I like the idea for power users. I want to know if it's worth implementing this feature. I am really interested in the technical challenge of exercising one of the benefits of hexagonal architecture.
The text was updated successfully, but these errors were encountered: