Since the all option is handled now as a NAME token. The syntax check is now failing because since this is a NAME token and because of the entityList rule in the parser, it tries to check the name syntax as a entity name. However ENTITY_NAME_PATTERN does not match all making it fail.
Motivation for or Use Case
When the jhipster-core is linked to the generator, the tests fails in the generator due to a test using a jdl containing service all with serviceImpl.
Reproduce the error
Link the jhipster-core (master) on the generator-jhipster (master) and launch the generator tests.
Overview of the issue
Since the
all
option is handled now as a NAME token. The syntax check is now failing because since this is a NAME token and because of the entityList rule in the parser, it tries to check the name syntax as a entity name. However ENTITY_NAME_PATTERN does not matchall
making it fail.Motivation for or Use Case
When the jhipster-core is linked to the generator, the tests fails in the generator due to a test using a jdl containing
service all with serviceImpl
.Reproduce the error
Link the jhipster-core (master) on the generator-jhipster (master) and launch the generator tests.
Related issues
https://github.com/jhipster/jhipster-core/commit/19395457011595d9245bcc8952eecc5e86d3f2c5
Suggest a Fix
Either revert the all handling back or add the edge case of all option in the syntax checking but we might need to fix some other problems too.
JHipster Version(s)
Master version
JHipster configuration
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryBrowsers and Operating System