[Hive Explorer] incorrectly displays subgraph owner of a field when a type is used with @external

[rickbijkerk]

we have a setup similar to this where there's a subgraph A which defines the Product and ProductWeight type

#Subgraph A
type Product @key(fields: "id") {
    id: ID!
    weight: ProductWeight!
}

type ProductWeight  {
    weight: Int!
    // .. 
}

and a subgraph B which uses the ProductWeight data to enrich the Product type

#Subgraph B
type Product @key (fields: "id"){
    id: ID!
    weight: ProductWeight! @external
    shippingCosts: Int! @requires(fields: "weight { id }")
}


type ProductWeight @external {
    id: ID!
}

Problem:
based on the schema above i would expect hive to display Subgraph A to be the owner of the weight field on Product and all of ProductWeight fields, however in reality Hive displays Subgraph B to be the owner of the weight field and of the id field on the ProductWeight type

Expected outcome:
Hive should exclude subgraphs that have a field marked as @external when looking for the owner.

(Note: currently hive does correctly mark both subgraph A and B as owner of the ProductWeight Type which i think makes sense as it makes it easy to find usages of certain types)

If you need more info let me know!

[n1ru4l]

I just tried to reproduce it based on your example using the following schemas:

Subgraph A

extend schema @link(url: "https://specs.apollo.dev/federation/v2.3", import: ["@key"])

type Product @key(fields: "id") {
  id: ID!
  weight: ProductWeight!
}

type ProductWeight {
  id: ID!
  weight: Int!
}

type Query {
  a: Product!
  g: ProductWeight!
}

Subgraph B

extend schema
  @link(url: "https://specs.apollo.dev/federation/v2.3", import: ["@key", "@external", "@requires"])

type Product @key(fields: "id") {
  id: ID!
  weight: ProductWeight! @external
  shippingCosts: Int! @requires(fields: "weight { id }")
}

type ProductWeight @external {
  id: ID!
}

type Query {
  c: Product!
}

As you can see in this explorer screenshot, this is not really showing the outcome you described. Can you share an example that showcases the described issue?

[n1ru4l]

I also added a unit test to confirm this behaviour: #7097