Skip to content

Conversation

@leggetter
Copy link
Collaborator

The x-speakeasy-pagination configuration was referencing 'next_cursor' but should reference 'next' (the original OpenAPI parameter name) because x-speakeasy-name-override only affects generated code, not the OpenAPI spec itself. The pagination configuration is validated against the OpenAPI spec, so it must use the actual parameter names from the spec.

…enAPI parameter name

The x-speakeasy-pagination configuration was referencing 'next_cursor' but
should reference 'next' (the original OpenAPI parameter name) because
x-speakeasy-name-override only affects generated code, not the OpenAPI spec
itself. The pagination configuration is validated against the OpenAPI spec,
so it must use the actual parameter names from the spec.
Copilot AI review requested due to automatic review settings January 16, 2026 13:04
@vercel
Copy link

vercel bot commented Jan 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
outpost-docs Ready Ready Preview, Comment Jan 16, 2026 1:04pm
outpost-website Building Building Preview, Comment Jan 16, 2026 1:04pm

Review with Vercel Agent

@leggetter leggetter merged commit 002cf66 into main Jan 16, 2026
5 checks passed
@leggetter leggetter deleted the feat/sdk-generation-update branch January 16, 2026 13:04
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request fixes a bug in the Speakeasy SDK pagination configuration for Python. The pagination configuration incorrectly referenced next_cursor (the renamed parameter in generated code) instead of next (the actual OpenAPI parameter name). Since x-speakeasy-name-override only affects code generation and not the OpenAPI spec itself, the pagination configuration must reference the original parameter names.

Changes:

  • Updated pagination configuration to use next instead of next_cursor in both events endpoints
  • Added explanatory comments documenting why the original parameter name must be used

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants