Clarify populate and pagination combination#3048
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Thank you very much again, @singhvishalkr. Esp. for fixing an open issue! I'm just waiting for you to fix the encoding (see inline comments), and I'll approve this one as well. I fixed the PR title according to our |
|
Thank you for the review, @pwizla! I've fixed the encoding on both lines and applied your style suggestion for the pagination paragraph. Ready for another look. |
|
Perfect! I'm merging it now, thank you! |
* docs(rest): clarify populate and pagination interaction * Apply suggestion from @pwizla * fix: resolve encoding and apply style guide suggestion --------- Co-authored-by: Pierre Wizla <pwizla+github@gmail.com>
|
Hi again, @singhvishalkr. You submitted several PRs this week, thank you very much for this, we at Strapi really appreciate it. I was wondering if you've heard about our Documentation Contribution Program? You're supposed to be rewarded based on the number of PRs and their effort, with points you can exchange on our Strapi Shop. I tried to trigger to automation, have you received any email? |
|
Hi Pierre,
Thanks for reaching out and for the kind words—I really appreciate it.
I’ve checked again just now, and I haven’t received any email regarding the
Documentation Contribution Program. Please let me know if there’s anything
I should do on my end.
And thanks again for taking the time to inform me and double-check this.
Regards,
Vishal
…On Wed, 15 Apr 2026 at 8:58 PM, Pierre Wizla ***@***.***> wrote:
*pwizla* left a comment (strapi/documentation#3048)
<#3048 (comment)>
Hi again, @singhvishalkr <https://github.com/singhvishalkr>. You
submitted several PRs this week, thank you very much for this, we at Strapi
really appreciate it. I was wondering if you've heard about our Documentation
Contribution Program
<https://www.notion.so/strapi/Documentation-Contribution-Program-1d08f359807480d480fdde68bb7a5a71>?
You're supposed to be rewarded based on the number and lengths of your PRs,
with points you can exchange on our Strapi Shop. I tried to trigger to
automation, have you received any email?
—
Reply to this email directly, view it on GitHub
<#3048 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZVZW5U5RBGSVTPGWMJDKHD4V6TATAVCNFSM6AAAAACXVDEZXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENJTGM2DCMJVGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
I see, we might have an issue with our automation, then. I'll escalate this and will keep you posted 😊 |
What does this PR change?
Replaces the misleading blanket note stating that population and pagination operators cannot be combined with a precise clarification of what is and isn't supported.
Before: The note implied that
populateandpaginationare mutually exclusive, which is incorrect -- top-level pagination works alongside populate.After: The note clarifies that top-level pagination works with populate, but pagination parameters cannot be applied within populated relations (nested pagination).
Closes #1585
How to verify
GET /api/articles?populate=*&pagination[page]=1&pagination[pageSize]=10returns paginated results with populated relations