-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Audit Relationship fields implementation #43
Comments
Further to-do items once the basics have landed:
Then we should review the design for how reverse relationships are surfaced in the Admin UI. In Keystone 4 we had a separate section below the item form, we could go with that or do something different 🤷♂️ |
Do you mean this? {
allPosts(author: {name: "Jed"}) {
id
}
} I'm going to work on this now as there are two projects that require it. |
@jesstelford did this get resolved? or is it still pending? |
I'm not sure. It's been a while since I touched it and I know other work has been done elsewhere. Probably needs an audit to see what's left. |
I'm also interested in how the relationship type maps into relational DBs; see #330. |
It looks like there hasn't been any activity here in over 6 months. Sorry about that! We've flagged this issue for special attention. It wil be manually reviewed by maintainers, not automatically closed. If you have any additional information please leave us a comment. It really helps! Thank you for you contribution. :) |
Most issues here solved. Making #2885 the canonical issue for additional relationship views. |
To finish implementing Relationships, we need to:
id
of relationship field values, and don't just expecting a stringThe last task will rely on having the ability to implement custom cell components ("views") for field types that are used by the List view in the Admin UI, which is technically possible but hasn't been done yet.
The text was updated successfully, but these errors were encountered: