Behavior for @inaccessible and @internal in combination with unions, interfaces and enum values.

[michaelstaib]

Example 1

union SearchResult = User | Group

type User @inaccessible { id: ID! }


type Query {
    search(text: String!): SearchResult
}

enum SearchResult
{
    FOUND
    NOT_FOUND @inaccessible
}

type Query {
    search(text: String!): SearchResult
}

what does apollo do in this case?

a) Composition error as we could not have runtime errors (when user is returned)
b) Composition warning and returning null at runtime
c) No composition error and returning null at runtime
d) No composition error and throwing error at runtime (edited)

[dariuszkuc]

Current Apollo behavior

• example 1

  • API schema results in union SearchResult = Group (i.e. User is not available in the schema)
  • no composition warnings
  • if subgraph were to return User that would be a runtime error

• example 2

  • API schema exposes only enum SearchResult { FOUND }
  • no composition warnings
  • returning NOT_FOUND results in runtime error

[dariuszkuc]

Option e - composition warning + runtime error

[glen-84]

Should we close this, and open a separate issue about adding a validation rule?