I found bugs in JHipster 6.0 and 6.1
Bugs in 6.0…
When I worked on the second part of my “Better Java Projects Faster with JHipster and Docker” tutorial, I found three bugs.
- The first bug concerned a new feature in JHipster 6.0, the so-called fake data. Yeah, I know, but I didn’t call it that, the JHipster folks did! Anyway, JHipster creates random data for entities defined in your JDL file. Github issue #9721 details some ways in which that fake data was wrong and actually broke your application.
- The next issue, #9726, was much less severe. It just describes some unnecessary Java compiler warnings during the DTO mapper generation.
- The final issue, #9726, was more impactful again: Under admittedly rare circumstances — a relationship between two entities which was required on both sides — the Angular code for creating / updating said entities was partially broken.
…and fixes in 6.1
I can happily report that the JHipster team fixed these three bugs in JHipster 6.1.
But wait, there’s more!
Unfortunately, I found two more bugs when verifying those three issues:
- Issue #9990 shows how JHipster generates fake data doesn’t honor the unique ID requirement of my entity.
- Issue #9991 demonstrates what a
!can make: There is one too many in the Typescript class for an Angular create / update screen, so the code goes into an
elsebranch where it shouldn’t.
No surprises in Java 17 LTS, Oracle Java free in production again, Java LTS every 2 years, Eclipse IDE 2021–09, Spring Data 2021.0.5 & 2020.0.13.
Sign up to my newsletter