Sasha 3fb81ef43b fix(graphql): nextPage and prevPage are non nullable even though they can be null sometimes (#12201) ...

This PR introduced https://github.com/payloadcms/payload/pull/11952
improvement for graphql schema with making fields of the `Paginated<T>`
interface non-nullable.

However, there are a few special ones - `nextPage` and `prevPage`. They
can be `null` when:
The result returned 0 docs.
The result returned `x` docs, but in the DB we don't have `x+1` doc.
Thus, `nextPage` will be `null`. The result will have `nextPage: null`.
Finally, when we query 1st page, `prevPage` is `null` as well.

<img width="873" alt="image"
src="https://github.com/user-attachments/assets/04d04b13-ac26-4fc1-b421-b5f86efc9b65"
/>

2025-05-05 09:12:44 -04:00

..

config.ts

fix(graphql): sanitize graphql field names for schema generation (#11556)

2025-03-07 14:43:09 +00:00

eslint.config.js

feat(graphql): graphQL custom field complexity and validationRules (#9955)

2024-12-13 15:03:57 -05:00

int.spec.ts

fix(graphql): nextPage and prevPage are non nullable even though they can be null sometimes (#12201)

2025-05-05 09:12:44 -04:00

payload-types.ts

chore: run dev:generate-types (#11994)

2025-04-08 17:25:29 -03:00

schema.graphql

fix(graphql): sanitize graphql field names for schema generation (#11556)

2025-03-07 14:43:09 +00:00

tsconfig.eslint.json

feat(graphql): graphQL custom field complexity and validationRules (#9955)

2024-12-13 15:03:57 -05:00

tsconfig.json

feat(graphql): graphQL custom field complexity and validationRules (#9955)

2024-12-13 15:03:57 -05:00