-
Move some of the common code to JDL so that we can use it in JHUML and the sub generator
This would make JDL act like a parent library kind of thing for all Jhipster projects that requires these info.…
-
The following does not fill in the relationship fields for any entities in the .json files that are generated.
entity Organization {
name String required,
description String,
createdDate…
-
##### **Overview of the issue**
Generate entity with pattern validation
ex:
entity E{
test String pattern("$\d+^")
}
Result:
class E{
....
@Pattern(regexp = "undefined")
String test;
....
}
###…
-
**Overview of the issue**
import JDL subgenerator updates changelogdate in .json files for all the entities (while regenerating entity) instead of only the modified entity. Because of which conflict …
-
##### **Overview of the issue**
The JDL documentation mention keywords like 'microservice' and 'skipClient'. The JDL Studio it self does not recognise them neither does the 'import-jdl' subgenerator…
-
In the grammar, the pegjs parser must be built again.
[This](https://github.com/jhipster/jhipster-domain-language/blob/dslparser/lib/dsl/jdl_parser.js#L224) must be replaced as well, and [this](https:…
-
The work in the "coreobjects" branch is almost done, save the last object that should encapsulate every other object.
This is a pseudo-roadmap of what needs to be done afterwards:
- [x] Migrate the JD…
-
If I create the example:
```
entity Owner {}
entity Car {}
relationship OneToMany {
Owner{car} to Car{owner}
}
```
Jhipster creates Entities for Owner and Car, and I can create Cars without owner.…
-
##### **Overview of the issue**
import JDL subgenerator updates all entity changelogdate in **.json** files while regenerating entity(instead of only the modified entity). Because of which conflict …
-
Currently if I create a one to many relationship (Owner-Car), I can create records in the many part with the relationship field empty (i.e. Car without an owner).
I was told [in the jhipster domain l…