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
Thanks for submitting this issue. I do think there's a lot that could be done to improve the explorer. And improving searchability/filtering is one of those things.
It sounds like you want to be able to select a subgraph, as well as toggle "unused" or "deprecated" so that a subgraph owner can see which parts of their schema could be cleaned up.
I think entity types could be an edge case for this.
e.g. An unused type may still be referenced by another subgraph and therefore couldn't be removed.
I'm curious if when filtering by subgraph, if youd like to also see external fields on a subgraph's entity type(s)? Or would that only add confusion?
It sounds like you want to be able to select a subgraph, as well as toggle "unused" or "deprecated" so that a subgraph owner can see which parts of their schema could be cleaned up.
Pretty much exactly this, yeah.
To be honest I hadn't considered the full complexity of the various iterations possible with different federation directives.
My first instinct was to follow what's already visible on the Explorer UI, which I believe is simply showing which graphs contribute which fields (e.g. the key field would show all subgraphs).
I'm not totally familiar with Hive's schema, but I believe this is roughly possible through the GraphQLField type, then we could grab the SupergraphMetadata.ownedByServiceNames.
It would be useful to see the rich view of types/fields broken down by subgraph(s).
This could pair nicely with the unused/deprecated filter so subgraph owners can see which parts to tidy up.
The text was updated successfully, but these errors were encountered: