Skip to content

fix(vapi): add cursor-based pagination to propDefinitions#21135

Open
favzqn wants to merge 1 commit into
PipedreamHQ:masterfrom
favzqn:issue-21085-vapi-cursor-pagination
Open

fix(vapi): add cursor-based pagination to propDefinitions#21135
favzqn wants to merge 1 commit into
PipedreamHQ:masterfrom
favzqn:issue-21085-vapi-cursor-pagination

Conversation

@favzqn

@favzqn favzqn commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Closes #21085.

The three propDefinitions (phoneNumberId, assistantId, squadId) previously fetched only a single page of results. This adds createdAtLt cursor pagination using the prevContext pattern so accounts with >1000 resources can load more results in the dropdown.

Changes

  • vapi.app.mjs: Each async options() now accepts prevContext, passes createdAtLt as a query param for the next page, and returns { options, context } to support load-more
  • package.json: Version bump 0.3.0 -> 0.3.1

Validation

  • pnpm eslint components/vapi — passes clean
  • node --check — passes
  • node scripts/build-components.mjs components/vapi — passes

The phoneNumberId, assistantId, and squadId async options previously
fetched only a single page. Add createdAtLt cursor pagination using
the prevContext pattern so accounts with >1000 resources can load more.

Closes PipedreamHQ#21085
@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

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

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
pipedream-docs-redirect-do-not-edit Ignored Ignored Jun 11, 2026 10:39am

Request Review

@ashwins01 ashwins01 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Hi @favzqn, thank you for you contribution! Since there are changes in the vapi.app.mjs file, the corresponding actions need their versions to be updated for them to be reviewed and tested properly. Can you resolve conflicts and update the package versions and do a round of testing for the list-* actions ?
Sharing our contribution guidelines for your reference: https://pipedream.com/docs/components/contributing/guidelines

Also, since the return shape has changed, the caller sites need to be modified to utilise the changed options return change aswell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

prioritized Prioritized issue User submitted Submitted by a user

Projects

None yet

Development

Successfully merging this pull request may close these issues.

vapi: add cursor-based pagination to phoneNumberId, assistantId, and squadId propDefinitions

5 participants