Closed nicolas63 closed 11 months ago
If this is a blocker, we can easily revert at the blueprint for now.
It's not a blocker but in the blueprint we don't change this code, so i think you have the same problem in the main generator
JHipster has completed the sample check
.yo-rc.json
: valid
Entities JDL: valid
Application: successfully generated
Frontend check: success
Backend check: success
E2E check: failure
Do you have an idea for fixing ?
This bug is interesting. Location
entity instance is matching location
from location.href
.
The correct fix would be to generate a tsEntityInstance
prefixed with jhiPrefix
.
Overview of the issue
Since the update from JHipster v8.0.0-rc.1 to JHipster 8.0.0 on the dotnet blueprint, I've encountered an error in the e2e tests.
My entity is failing during the deletion process, and I believe it's due to this modification. I have retried with the old code, and it works well
Reproduce the error
I'm not sure why only this entity is experiencing the problem
Suggest a Fix
JHipster configuration, a
.yo-rc.json
file generated in the root folder.yo-rc.json file
JDL for the Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryJDL entity definitions
Browsers and Operating System