| name | ai-memory-coding-conventions |
| description | Project coding conventions extracted from chat history. Load when writing new code, naming things, designing APIs, or reviewing PRs. Topics: Cursor pagination is mandatory for all paged GraphQL endpoints. |
Coding Conventions
Auto-generated by ai-memory from AI chat history. Edit memories via ai-memory list / extract / resolve rather than this file — it is fully regenerated on every ai-memory rules --target skills.
Cursor pagination is mandatory for all paged GraphQL endpoints
Every paged GraphQL endpoint MUST use Relay-style cursor pagination (edges / node / cursor + pageInfo.hasNextPage). Choose first + after as the canonical pair; reject last + before unless explicitly justified per endpoint. CI lint rule will enforce on new schema.
Why: Cursor pagination is stable across mutations and aligns with the Apollo/Relay tooling already in use. Migration of existing offset endpoints exposes both shapes for one minor version so consumers can switch over without breakage.
Rejected: Offset/limit (rejected, see Context). Page-token-only (rejected — no cursor opacity guarantee, leaks server state). Custom cursor scheme (rejected — no benefit over Relay spec).
