Skip to content

docs: add V2 pagination requirements to cursor rule#1550

Merged
TheLastCicada merged 1 commit into
v2-rc2from
docs/v2-pagination-rule
Mar 24, 2026
Merged

docs: add V2 pagination requirements to cursor rule#1550
TheLastCicada merged 1 commit into
v2-rc2from
docs/v2-pagination-rule

Conversation

@TheLastCicada

@TheLastCicada TheLastCicada commented Mar 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Documents which V2 list endpoints require page and limit query parameters in the .cursor/rules/v2.mdc rule
  • Covers the three cases: always required (most entity endpoints), conditionally required (project/unit skip when xls=true), and not required (organizations, governance, offer, filestore, health/*)
  • Prevents a recurring CI failure where API calls without pagination params silently returned 400

Test plan

  • N/A — cursor rule only, no code changes

Note

Low Risk
Documentation-only change that clarifies which V2 list endpoints require page/limit, with no runtime behavior or data-handling impact.

Overview
Clarifies V2 API list pagination expectations in .cursor/rules/v2.mdc, explicitly calling out which entity endpoints enforce paginationSchema, the project/unit exception when xls=true, and which endpoints do not require page/limit. This is intended to prevent recurring 400s/CI failures from missing pagination query params.

Written by Cursor Bugbot for commit d3f8f38. This will update automatically on new commits. Configure here.

@TheLastCicada TheLastCicada merged commit d8c9fb0 into v2-rc2 Mar 24, 2026
21 of 24 checks passed
@TheLastCicada TheLastCicada deleted the docs/v2-pagination-rule branch March 24, 2026 23:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant