-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Entities with JpaRepository only #17436
Comments
Cc @mshima as you're our expert on this part. What do you think? Cc @MathieuAA too |
It's easy to do. Again, the generation part is done by the generator and there's no change to do in the "JDL part" of the code base: once the .JSON files are generated, it's up to a generator to read the JSON entity files and do its magic. |
Can somewhat be accomplished by Missing the I will try an entity only jdl. |
Interesting! Will try it soon. |
Application is currently required to parse the jdl.
|
@mshima Yes, it's kinda mandatory so as to validate the provided entities. Removing this check can easily be done though |
So I tried the following with the current version. jhipster import-jdl --skip-client --ignore-application model\21-points_mvn.jh 21-points_mvn.jh is the file 21-points.jh from the jdl-samples project where the build tool was set to maven. The convent of the directory after the command is run is as follows So the functionality is "there". I can not imagine anyone who would say no to generated rest controllers and repositories for their entities. Hehe. :D |
@nomuna : it depends on your needs and on your project:
|
@pascalgrimaud So basically if you add another option to disable the rest stuff and repository stuff it would be enough, yes? At the moment whoever needs this functionality could remove the rest/repository code. Not saying that the ticket does not make sense or anything. Just pointing out what is there and see how far I can go using the already available means so that what can and should be done is clarified. |
@nomuna : here some use cases 1st use case:
2nd use case:
So as discussed in the mailing list, we think it could be a great option to use the JDL in existing Spring Boot projects, without the need of JHipster projects. |
Hello, If you implement it, please keep in mind the discussion we had here: #14416 IMHO inclusive options will fix one pain point we'll face in regard to exclusive syntax |
I don't plan to implement it and not sure if we should do it. |
Followed my last comment, no need to implement it |
Overview of the feature request
It could be a 1st step of @jdubois's idea in the mailing list.
I wonder if we could use the JDL to generate only the entities and jpa part, and ignoring Service, DTO, Rest, front, etc
Maybe we could only keep the liquibase part, I don't know.
Motivation for or Use Case
If the JDL can work in all Spring Boot projects, without the requirement of the base of JHipster project, it will be a killer feature.
Related issues or PR
The text was updated successfully, but these errors were encountered: