-
Notifications
You must be signed in to change notification settings - Fork 1.1k
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Component Relation Publication State needs to be set at each level #917
Comments
Hey, is the issue the fact that you've to add a |
Ah this is one of the undocumented changes from v3 where it ran globally. |
Indeed. In V3 we were sharing the state to child resolvers but it didn't really make sense in a GraphQL architecture where every resolver should be as isolated as possible. Sorry for the undocumented change, it must've been lost among all the other things 🙏 |
No problem, I'll transfer this over to the documentation repo to have it added into the docs. |
|
It's been over a year and this issue is still a big problem and unsolved. Please fix it in future releases. |
Bug report
Required System information
Describe the bug
Publication State isn't applied in component fields when making a graphql query.
Steps to reproduce the behavior
alloys
st
tp
tp_with_st
Make a GraphQL query, querying alloys and notice that the publication state of the one-to-one related elements on the component is not respected.
Expected behavior
For all element publication state to be respected.
Screenshots
The text was updated successfully, but these errors were encountered: