Document UserOrderByInput about opencrud HOT 5 OPEN

I found one here:

enum UserOrderByInput {
  # ascending and descending for all non-list scalar fields
}

query { users(orderBy: UserOrderByInput): [User!]}

query { users(orderBy: NAME_ASC) {name}}

I don't know if I'm a fan of NAME_ASC though? What about { name : 1 } or { name: -1 } like in Mongo?

from opencrud.

The naming fieldName_ASC is concise and consistant with other parts of OpenCRUD like filtering.

There is an issue if we need to sort on several fields or on a field from a relation.

Proposition : orderBy could accept a list of fields:

query { users(orderBy: [UserOrderByInput] ): [User!]}
query { users(orderBy: [role_ASC, name_DESC] ) {name}}

GitHub style:

query  {
  user(login:"GromNaN") {
    issues(first:100, orderBy:{field:COMMENTS, direction:ASC}) {
      edges {
        node {
          id
          title
        }
      }
    }
  }
}

from opencrud.

Could the orderBy input type be a union, like this?

orderBy: UserOrderByInput! | [UserOrderByInput!]!

Assuming GraphiQL and other tools handle this right, they would still provide auto-completion for orderBy this way, especially in cases where only one attribute is needed.

from opencrud.

Input type be a union is not supported (yet). graphql/graphql-spec#488

from opencrud.

While GraphQL does not support union input types, a single input element is actually coerced into a single item list, so in this case we don't need a union type :-) See: prisma/prisma#95 (comment)

from opencrud.