Repository navigation
Bounded Pagination in PowerShell Tools for Agents - #470
tridev-tej wants to merge 4 commits into
Conversation
✅ Deploy Preview for powershellorg ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
There's a lot of potential with this article and I think this is a good topic to cover. Please consider tweaking the intro to make it clear what the problem is and why I understanding how to solve it is important.
There's several large files you're asking folks to copy and paste to their machine. If you want to improve the likelihood of them working through this article, you're going to need to document the code a bit more.
There are also several instances of bash mentioned. It's safe to assume the users will have PowerShell available, and by sticking to that over bash you'll have a cross platform article.
There was a problem hiding this comment.
🟡 Changes recommended
The decimal parsing uses the caller’s locale, causing cultures such as fr-FR to abort the adapter and verifier before budget-validation probes run; both calls need InvariantCulture.
1 open issue
What changed in this PR
Adds a guest tutorial for issue #451 showing how PowerShell REST tools can enforce pagination budgets and report complete, partial, or failed results explicitly.
Changes:
- Defines page and result contracts with request limits, item limits, and cycle detection.
- Provides a local API, a complete PowerShell reader, and walkthrough examples.
- Includes verification scripts for boundary cases and failures, plus explanations of the limits these budgets cannot enforce.
| File | Description |
|---|---|
| content/articles/2026/10/bounded-pagination-in-powershell-tools-for-agents/index.md | Adds the bounded-pagination tutorial, runnable examples, and verification harness. |
Review effort: Balanced
Signed-off-by: Tejesh Vaish <188414140+tridev-tej@users.noreply.github.com>
|
The standalone increment With a single-request JSON array, Earlier draft changes:
Earlier walkthrough and help checks covered macOS and Ubuntu. Numeric checks ran under |
There was a problem hiding this comment.
🟡 Changes recommended
Two critical active issues remain: a post-increment leaks a truthy pipeline value that can corrupt pagination status, and single-request JSON deserialization can iterate hashtable entries instead of invoking the intended request.
2 open issues
1 resolved since last review
Review effort: Lite
| if (-not $State.Seen.Add($State.Cursor)) { | ||
| return Set-PageStop $State 'Error' 'RepeatedToken' | ||
| } | ||
| $State.RequestsAttempted++ |
|
|
||
| $ErrorActionPreference = 'Stop' | ||
| . "$PSScriptRoot/Get-BoundedPage.ps1" | ||
| $requests = Get-Content -Raw -LiteralPath $RequestFile | ConvertFrom-Json -AsHashtable |
|
This is still set as a draft PR. Are you ready for it to be reviewed? Also check out the copilot comments. |
Guest article for #451
Shows how to bound paginated API reads by page and item budgets, with explicit completion and error states. Includes a local API and reader covering cyclic cursors, malformed pages and partial results.