-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mappings don't support 1:N on reverse relationships #11838
Mappings don't support 1:N on reverse relationships #11838
Comments
@pieh it seems like you have most context about this |
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Not stale. |
@pauleveritt This might have been fixed in latest gatsby, I wonder if you could see if it works for you. |
@freiksenet I just tried (albeit with |
Description
When using a
mapping
ingatsby-config.js
, reverse relationships work as described in the docs but only for a 1:1 relationship. A 1:N relationship doesn't return an array, it just returns a single value.This was discussed also in #11151
Steps to reproduce
Here is a reproducible repo that illustrates the bug as well has links to a video illustrating it.
Expected result
When expanding the node in a page query, I should get an array of items. Meaning, it should work the same as a forward relationship for 1:N.
Actual result
I only get a single value.
The text was updated successfully, but these errors were encountered: