Skip to content

Filter by subgraph in explorer view #6459

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

Open
RMHonor opened this issue Feb 2, 2025 · 2 comments
Open

Filter by subgraph in explorer view #6459

RMHonor opened this issue Feb 2, 2025 · 2 comments

Comments

@RMHonor
Copy link

RMHonor commented Feb 2, 2025

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.

@jdolle
Copy link
Collaborator

jdolle commented Feb 7, 2025

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?

@RMHonor
Copy link
Author

RMHonor commented Feb 10, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants