Consistency Issues with GraphQL API
Proposal
A large Self-Managed Premium customer reported the following issue:
There is a lack of consistency in the naming and typing of many variables and fields. For example:
In this screenshot we have a query and a mutation. The results on the right are from the query. We have:
-
fullPath
andprojectPath
representing the same data - Three different typings for the
iid
depending on where it is being used/returned (String
,String!
, andID!
) -
ID!
type is either a full path, a number, or a gid identifier string, making it incredibly difficult to understand what the API actually wants for input fields
Edited by Dasha Foley