perses-code-review

To enforce pagination on List endpoints, you can run a Perses-domain code review that flags missing pagination as a blocker on Go API endpoint changes. It dispatches dedicated sub-reviewers to check Perses-specific API patterns and aggregates the findings.

Validating CUE schema packaging and JSON examples is handled by running a Perses-domain code review. It dispatches a dedicated CUE sub-reviewer to check schema conventions and aggregates findings to ensure compliance with Perses patterns.

Yes, you can review React frontend and Go backend changes together for Perses API conformance. The review dispatches per-file-type sub-reviewers for both TS and Go, aggregating findings to ensure domain alignment across the full stack.

The best way to lint dashboard definitions and check references in Perses is to run a domain-specific code review. It dispatches a dashboard resource sub-reviewer that validates dashboard definitions, checks references, and aggregates any linting findings.

Yes, the Perses code review works with CUE schemas and dashboard definitions simultaneously. It applies to changes touching schema files and dashboards, dispatching dedicated sub-reviewers for CUE and dashboard resources to enforce domain-specific invariants.

Your Perses code review flags missing pagination as a blocker because enforcing pagination on List endpoints is a required Perses-specific invariant. The review aggregates these findings to ensure project-scoped API patterns are strictly followed.