- Issue created by @Naitschi
- 🇨🇭Switzerland ayalon
You are right! Thanks for pointing this out. Due to some refactoring, the field was tripped out. I have now fixed this issue and pushed the code changes to the dev branch. Soon a new release will be published containing the fix.
- 🇨🇭Switzerland ayalon
Example:
query reverseReferences { entityById(entityType: USER, id: 1) { ... on User { reverseReference { query(entityType: NODE, referenceFields: ["field_user"]) { total items { label } } } } } }
Please note, that the field was renamed from
reverseReferences
toreverseReference
- Status changed to Fixed
11 months ago 5:00pm 25 January 2024