Jhipster conflicts with all entities after adding a new property to an entity

jhipster / generator-jhipster

JHipster is a development platform to quickly generate, develop, & deploy modern web applications & microservice architectures.

https://www.jhipster.tech

Apache License 2.0

21.54k stars 4.02k forks source link

Jhipster conflicts with all entities after adding a new property to an entity #17006

Closed sulaiman-allemyar closed 11 months ago

sulaiman-allemyar commented 2 years ago

After adding a new property to an entity, the Jhipster conflicts with all entities and you must resolve all conflicts which is too much time consuming. for example if you have two entities Product and Stock, then after adding a new property to Product the Jhipster conflicts with Stock also.

I have also used older versions of Jhipster 6.x.x but this issue was not on those versions. Is there any solution to this issue? I am Jhipster monolithic architecture.

github-actions[bot] commented 2 years ago

This issue is stale because it has been open 30 days with no activity. Our core developers tend to be more verbose on denying. If there is no negative comment, possibly this feature will be accepted. We are accepting PRs :smiley:. Comment or this will be closed in 7 days

Tcharl commented 2 years ago

Hi,

Sorry but I'm not able to reproduce: are you customizing your Stock entity in a way between regeneration? It's the current behaviour: entities are not meant to be modified.

Still, there's a potential good idea behind this one, but I've no idea about the feasibility:

if the jhipster version is the same than the one in the target project package.json
if the diff between the .jhipster/entity.json and the future one (the one that has been specified by the cli or the jdl) is empty
if the --force flag is not set then skip the generation for this entity.

your thought @pascalgrimaud?

pascalgrimaud commented 2 years ago

@Tcharl : it is similar to these tickets

First, using jdl + json only flag, then using jhipster entity with single entity should do the job

github-actions[bot] commented 11 months ago

This issue is stale because it has been open for too long without any activity. Due to the moving nature of jhipster generated application, bugs can become invalid. If this issue still applies please comment otherwise it will be closed in 7 days

sulaimanallemyar commented 8 months ago

I developed a project with Jhipster 7.0.1 and have still this issue and could not find the solution for this problem. I have more than 55 entities, after adding a new entity/field Jhipster conflicts with all 55 entities. This issue is in Jhipster 7.x.x series, not 6.x.x series. The Jhipster even conflicts with those entities which has no changes and is same as Jhipster generated them.