Wrap auto-completed list input values with square brackets if required

In Gatsby’s connections, you can add a sort input like the following:

allMarkdownRemark(sort: { fields: [frontmatter___title], order: DESC}) {
  edges {
    node {
      id
    }
  }
}

But in graphiql, it doesn’t enforce that fields must be an array so people regularly complain sorting is broken as they just add a field in the UI and then when they try to copy that into a project it won’t work.

Is there a reason graphiql is like this? It seems to be casting the single values to an array which is why it seems to work.

[OlegIlyenko]

If I understand what you are describing correctly, then this aspect is covered by the GraphQL spec:

If the value passed as an input to a list type is not a list and not the null value, it should be coerced as though the input was a list of size one, where the value passed is the only item in the list. This is to allow inputs that accept a “var args” to declare their input type as a list; if only one argument is passed (a common case), the client can just pass that value rather than constructing the list.

In other words, it is ok to skip list syntax (e.g. [...]) if list has only one element.

[coreyward]

+1 Currently Relay will cast a single value to a string; graphiql’s deviation from this causes incompatibilities.