Skip to content

Latest commit

 

History

History
152 lines (95 loc) · 27.5 KB

CHANGELOG.md

File metadata and controls

152 lines (95 loc) · 27.5 KB

@keystone-next/example-blog

2.0.8

Patch Changes

2.0.7

Patch Changes

2.0.6

Patch Changes

2.0.5

Patch Changes

2.0.4

Patch Changes

2.0.3

Patch Changes

2.0.2

Patch Changes

2.0.1

Patch Changes

  • #5797 a6a444acd Thanks @timleslie! - The GraphQL field _all<path>Meta { count } generated for many relationships has been deprecated in favour of a new field <path>Count, which directly returns the count.

    A posts relationship field would have the following field added to the API:

    postsCount(where: PostWhereInput! = {}): Int
  • #5792 319c19bd5 Thanks @timleslie! - Changed the type of the where argument to allItems to _allItemsMeta from type ItemWhereInput to ItemWhereInput! = {}.
  • #5850 5b02e8625 Thanks @timleslie! - The AND and OR operators of ItemWhereInput now accept non-null values, e.g. [ItemWhereInput!], rather than [ItemWhereInput].

  • #5767 02af04c03 Thanks @timleslie! - Deprecated the sortBy GraphQL filter. Updated the orderBy GraphQL filter with an improved API.

    Previously a User list's allUsers query would have the argument:

    orderBy: String

    The new API gives it the argument:

    orderBy: [UserOrderByInput!]! = []

    where

    input UserOrderByInput {
  id: OrderDirection
  name: OrderDirection
  score: OrderDirection
}

enum OrderDirection {
  asc
  desc
}

    Rather than writing allUsers(orderBy: "name_ASC") you now write allUsers(orderBy: { name: asc }). You can also now order by multiple fields, e.g. allUsers(orderBy: [{ score: asc }, { name: asc }]). Each UserOrderByInput must have exactly one key, or else an error will be returned.

  • #5791 9de71a9fb Thanks @timleslie! - Changed the return type of allItems(...) from [User] to [User!], as this API can never have null items in the return array.

2.0.0

Major Changes

Patch Changes

1.0.0

Major Changes

Patch Changes