Closed pascalgrimaud closed 5 years ago
I'm adding the $100 tag here as I really want the JDL import and the entity sub-generator to work the same
The reserved words are actually defined in jh core, so unless there is a logical difference in validation somewhere, this shouldn't have happened
On Tue, 4 Dec 2018, 6:08 pm Julien Dubois <notifications@github.com wrote:
I'm adding the $100 tag here as I really want the JDL import and the entity sub-generator to work the same
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jhipster/jhipster-core/issues/290#issuecomment-444178388, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDlF-ZdSTckrkPZcRpw0vVHxqN7Zt3Bks5u1qwegaJpZM4ZBGaA .
I can look at this issue, since I need to better understand how the generator interacts/uses jh core.
thanks @murdos The logic is here: https://github.com/jhipster/generator-jhipster/blob/master/generators/entity/index.js#L301-L307
I think we don't apply it during the import-jdl
Yes the reserved keywords are good, it's the validation that is different:
Not that bad actually Julien, just an inconsistent choice.Anyway, I'm surprised about all this as nobody seemed to be that annoyed by such a behaviour in the past. I'm working on greatly extending the jdl export and the v4 release right now and I have a lot on my plate, so if anyone wants to adjust the code in this repo, be my guest :)
Reported by @jdubois When using a reserved Keyword (like
group
) in a JDL file, we got this error:When using directly the sub-generator entity, we got a warning but we can still use the reserved keyword:
Both generation should be consistent.
Here my JDL: