listBundles: server-side filters (only_prey, is_viewed, only_new, only_unsaved)#8
Merged
Conversation
… only_unsaved)
The Flappie cloud /api/v1/bundles endpoint accepts the same filter
parameters used by the official mobile app's filter sheet:
only_prey={true,false} — restrict to prey / non-prey events
is_viewed={true,false} — restrict to viewed / unviewed bundles
only_new={true,false} — only never-seen bundles
only_unsaved={true,false} — only bundles not yet in a collection
sort_order={asc,desc} — alternate spelling of order_direction
These params live as raw string literals in the Flutter AOT snapshot
and weren't covered by the original static-analysis sweep. Verified
live: only_prey=true reduces a 40-event account to 2 matching records
in a single roundtrip.
ListBundlesOptions gains `onlyPrey`, `isViewed`, `onlyNew`,
`onlyUnsaved`. RequestOptions.query now accepts booleans.
CLI gains `--prey`, `--viewed`, `--new`, `--unsaved` flags on
`flappie bundles list`.
CLOUD_API.md and openapi.yaml updated.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
GET /api/v1/bundlesaccepts the same filter parameters the official mobile app's filter sheet uses:only_prey={true,false}is_viewed={true,false}only_new={true,false}only_unsaved={true,false}sort_order={asc,desc}order_directionThese literals live in
api_service.dart::getBundlesPagein the AOT snapshot and were missed by the original static-analysis sweep (which scanned URL literals but not the&xyz=query fragments inside the same function body).Surface changes
ListBundlesOptionsgainsonlyPrey,isViewed,onlyNew,onlyUnsaved.RequestOptions.querynow acceptsbooleanalongsidestring | number.flappie bundles list --prey true --viewed false --new --unsaved.CLOUD_API.md+openapi.yamlupdated.Verified live
Before: callers wanting prey-only had to paginate every page and filter client-side. After: one roundtrip.
🤖 Generated with Claude Code