You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until at least version 8.1.0, buttons for filtering the other side of the entity were generated (initial feature: #18370). This is at least in 8.5.0 not the case anymore, as the corresponding relationships are already filtered out beforehand, so the links are not generated anymore.
Motivation for or Use Case
Feature worked before and kind of all of the of the code for that is still in there.
Reproduce the error
Have an application with a ManyToOne / OneToMany /ManyToMany relationship using Angular as frontend.
Changes in #25140 are causing this, I think. Previously, the list of relationships passed to the client generator were unfiltered apart from the skipClient flag.
Suggest a Fix
get rid of the persistable/eagerload filtering here. Don't know, what effect this has elsewhere, should be tested - or only be changed for the Angular client in doubt:
<%_ for (constrelationshipofrelationships.filter(rel=>!rel.otherEntityIsEmbedded)) { _%>
<%_ if (relationship.otherEntity.jpaMetamodelFiltering&&relationship.otherEntity.paginationPagination&&relationship.collection&&!relationship.persistableRelationship) {
Overview of the issue
Until at least version 8.1.0, buttons for filtering the other side of the entity were generated (initial feature: #18370). This is at least in 8.5.0 not the case anymore, as the corresponding relationships are already filtered out beforehand, so the links are not generated anymore.
Motivation for or Use Case
Feature worked before and kind of all of the of the code for that is still in there.
Reproduce the error
Related issues
Changes in #25140 are causing this, I think. Previously, the list of relationships passed to the client generator were unfiltered apart from the
skipClient
flag.Suggest a Fix
get rid of the persistable/eagerload filtering here. Don't know, what effect this has elsewhere, should be tested - or only be changed for the Angular client in doubt:
generator-jhipster/generators/client/support/filter-entities.ts
Lines 25 to 29 in eee53c5
by the way, the parts in the html of the Angular client are still there though and there you can also see the the contradictionary conditions:
generator-jhipster/generators/angular/templates/src/main/webapp/app/entities/_entityFolder_/list/_entityFile_.component.html.ejs
Lines 178 to 191 in eee53c5
&& !persistableRelationship
(Angular code) vs.persistableRelationship
(filter-entities.ts)JHipster Version(s)
8.5.0
JHipster configuration
Entity configuration(s)
entityName.json
files generated in the.jhipster
directoryBrowsers and Operating System
The text was updated successfully, but these errors were encountered: