Add internal support for generators to implement jdl incremental generation for config and entities. #19989
Labels
area: feature request 💡
$$ bug-bounty $$
https://www.jhipster.tech/bug-bounties/
theme: jhipster-internals
$300
https://www.jhipster.tech/bug-bounties/
Milestone
Overview of the feature request
Back in JHipster 6, jdl command advertised that it only generates changed entities.
That was somewhat true, but it generated inconsistent source code.
The feature was jdl specific and had not support at generators. This was implemented by passing only changed entities to the generator, but it ignored application dependent configurations and relationships. Since the generator had no knowledge about others entities, relationships primaryKey and label types, that fall back to the default type that are application database dependent, were generated wrongly.
Due to this inconsistent behavior, this option was disabled.
For a consistent result, a jhipster application should be fully prepared.
At jhipster v8 the prepared application and entities are shared between the generators and fully consistent.
Now it's possible to add internal support to configuration and entities changes.
Configuration changes proposal:
Entity and entity changelogs proposal:
Motivation for or Use Case
Allow to generate new configuration and entities without overriding custom code.
Related issues or PR
#19978 (comment)
#19761
#8933
#19328
#17006
#14678
#13365
#13833
The text was updated successfully, but these errors were encountered: