The error for the hive dev and hive introspect commands can be misleading.
Both commands partially rely on introspecting federation subgraphs (via the Query._service field) or normal GraphQ introspection (via the GraphQL introspection query).
There is many error cases that could occur:
- GraphQL introspection is disabled
- The target is expected to be a federation subgraph but is not (
Query._service is missing)
- Network errors etc.
We need to revise the whole flow and errors and need to make sure it is obvious whether an error originates from HTTP calls/responses to the subgraph or our API (in case of the dev command).
Right now we have mixed logic and error classes and it can happen that something that an error originating from a subgraph is displayed as a Hive Console API error which is misleading.
In order to solve this technically, we first need to analyze which things can go wrong for each flow and define all the errors for those flows.
The error for the
hive devandhive introspectcommands can be misleading.Both commands partially rely on introspecting federation subgraphs (via the
Query._servicefield) or normal GraphQ introspection (via the GraphQL introspection query).There is many error cases that could occur:
Query._serviceis missing)We need to revise the whole flow and errors and need to make sure it is obvious whether an error originates from HTTP calls/responses to the subgraph or our API (in case of the
devcommand).Right now we have mixed logic and error classes and it can happen that something that an error originating from a subgraph is displayed as a Hive Console API error which is misleading.
In order to solve this technically, we first need to analyze which things can go wrong for each flow and define all the errors for those flows.