1. Naming rules
2. Type rules
- 2.1. Use custom scalar types if you want to declare fields or args with specific semantic value.
- 2.2. Use Enum for fields which contain a specific set of values.
3. Field Rules (Output)
4. Argument rules (Input)
5. Rules of lists
6. Mutation rules
7. Rules of linkages between types (relationships)
- 7.1. GraphQL schema should be "hairy"
8. Authorization
- 8.1. Schema diffing based authorization
9. Other rules
- 10.1. Use markdown for documentation
A. Appendix
- A-1 Useful links
Credits

5. Rules of lists

I never saw an API that does not return a list of items. Or it's page by page or something built on cursors for infinite lists. Lists should be filtered, sorted, and the number of returned items should be limited. GraphQL itself does not limit the freedom of implementation, but in order to form a certain uniformity, it is necessary to have a standard.

5.1. To filter the lists, use the filter argument, which contains all the available filters.

5.2. Use argument sort of type Enum or [Enum!] for listings sorting.

5.3. Use limit with default value and skip to limit number of returned items in list.

5.4. Use page, perPage args for pagination and return output type with items (array of elements) and pageInfo (meta-data).

5.5. For infinite lists (infinite scroll) use Relay Cursor Connections Specification