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
For reproducing purposes, lets assume that we have 2 APIs pointing to 1 Bundle which Bundle has 1 Destination.
If we call /v0/consumptionBundles?$expand=destinations everything is OK -> we receive 1 Bundle with 1 Destination.
However, if we call /v0/apis?$expand=consumptionBundles($expand=destinations) there are duplicate Destinations in the response -> we receive 2 APIs (OK) with 1 Bundle in each (OK) with 2 same Destinations in each Bundle (should be 1 Dest):
Note: this issue may sound similar to this one I recently opened, but there the problem was that we had missing JOIN columns which affected the uniqueness in the response which is not the case here.
The text was updated successfully, but these errors were encountered:
Hello,
We have
Bundle
entity in our domain which hasManyToMany
relation to bothAPI
andDestination
entities:Bundle
API
Destination
For reproducing purposes, lets assume that we have 2
APIs
pointing to 1Bundle
which Bundle has 1Destination
.If we call
/v0/consumptionBundles?$expand=destinations
everything is OK -> we receive 1Bundle
with 1Destination
.However, if we call
/v0/apis?$expand=consumptionBundles($expand=destinations)
there are duplicateDestinations
in the response -> we receive 2APIs
(OK) with 1Bundle
in each (OK) with 2 sameDestinations
in each Bundle (should be 1 Dest):To locally reproduce this issue, you can:
Note: this issue may sound similar to this one I recently opened, but there the problem was that we had missing JOIN columns which affected the uniqueness in the response which is not the case here.
The text was updated successfully, but these errors were encountered: