CODEWITHSUNDEEP
jhipster
Florian Reisinger
Florian Reisinger

Reputation: 3108

Jhipster - How not to override manual edits

I know it is the most basic question. In the video tutorial you can see a change in one Java file http://www.jhipster.tech/video-tutorial/

This change was "a user can only see his projects, except if he is the admin". This is only a minor change and works with the schema.

Now I want to extend the schema and I perform

a) only compatible changes (adding new tables and relation)

b) also some incompatible changes (e.g. fixing a typo in a table name)

My question: How does jHipsetr support such a evolution in the model with compatible and incompatible changes?

Regarding a) it should be possible to perform a kind of "merge" as you know the current model + changes and future model. Can this kind of evolution even be automated?

Regarding b) some things (like propagating table name changes) might even be possible to be automated

I am asking because I do not know how evolution in a model driven engineering approach is supported by jhipster.

Thank you for your answer,

Florian

Upvotes: 1

Views: 283

Answers (1)

Gaël Marziou
Gaël Marziou

Reputation: 16294

If you want to keep your manual changes, the jhipster upgrade command uses git to merge them with code evolutions in generator. Otherwise some coding conventions help a lot. You can see a presentation (in French) from Altissia about their coding conventions, slides with code examples could be read by non French speaking people.

Upvotes: 1

Related Questions