Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support campaign user pagination #1462

Merged
merged 6 commits into from
Feb 24, 2025
Merged

feat: support campaign user pagination #1462

merged 6 commits into from
Feb 24, 2025

Conversation

kanat
Copy link
Contributor

@kanat kanat commented Feb 1, 2025

Ticket

Related PR

CLA

  • I have signed the Stream CLA (required).
  • Code changes are tested

Description of the changes, What, Why and How?

Changelog

@kanat kanat changed the title [CHA-536] support campaign user pagination (feat) support campaign user pagination Feb 1, 2025
Copy link
Contributor

github-actions bot commented Feb 1, 2025

Size Change: +72 B (+0.01%)

Total Size: 525 kB

Filename Size Change
dist/browser.es.js 115 kB +16 B (+0.01%)
dist/browser.full-bundle.min.js 62.8 kB +10 B (+0.02%)
dist/browser.js 116 kB +14 B (+0.01%)
dist/index.es.js 115 kB +17 B (+0.01%)
dist/index.js 116 kB +15 B (+0.01%)

compressed-size-action

@kanat kanat changed the title (feat) support campaign user pagination feat: support campaign user pagination Feb 3, 2025
@kanat kanat requested a review from myandrienko February 3, 2025 22:35
{
campaign: CampaignResponse;
users: {
next?: string;
Copy link
Contributor

Choose a reason for hiding this comment

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

What are the returned cursors for when creating a campaign?

Copy link
Contributor Author

@kanat kanat Feb 4, 2025

Choose a reason for hiding this comment

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

If you pass more than 1,000 user_ids when creating a campaign, then in response you'll still get only 1,000 users with pager token

Copy link
Contributor

Choose a reason for hiding this comment

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

And when do you get next and prev?

@MartinCupela
Copy link
Contributor

@kanat I could not find any topic-related docs at https://github.com/GetStream/docs-content/pulls/kanat. Do you plan to add some?

@kanat
Copy link
Contributor Author

kanat commented Feb 4, 2025

Hey @MartinCupela, thank you for the feedback 👍

Yup, I add the docs changes by Today.

@kanat kanat requested a review from MartinCupela February 4, 2025 16:15
@kanat
Copy link
Contributor Author

kanat commented Feb 21, 2025

@MartinCupela the PR for docs is here:

@kanat kanat merged commit c629018 into master Feb 24, 2025
5 checks passed
@kanat kanat deleted the campaigns/limits branch February 24, 2025 15:04
github-actions bot pushed a commit that referenced this pull request Feb 26, 2025
## [8.57.0](v8.56.1...v8.57.0) (2025-02-26)

### Features

* add option to override channel.updated handler in ChannelManager ([#1471](#1471)) ([9082084](9082084))
* expand campaign stats ([#1470](#1470)) ([cc6404c](cc6404c))
* support campaign user pagination ([#1462](#1462)) ([c629018](c629018))
* support new X-Stream-Client format ([#1469](#1469)) ([fdb875b](fdb875b))
@stream-ci-bot
Copy link

🎉 This PR is included in version 8.57.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

arnautov-anton pushed a commit that referenced this pull request Feb 27, 2025
## [8.57.0](v8.56.1...v8.57.0) (2025-02-26)

### Features

* add option to override channel.updated handler in ChannelManager ([#1471](#1471)) ([9082084](9082084))
* expand campaign stats ([#1470](#1470)) ([cc6404c](cc6404c))
* support campaign user pagination ([#1462](#1462)) ([c629018](c629018))
* support new X-Stream-Client format ([#1469](#1469)) ([fdb875b](fdb875b))
@github-actions github-actions bot mentioned this pull request Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants