mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-10-20 05:06:31 +00:00
a30cfaa4c3
Both pagination query schemas validated only the upper bound, so
malformed pagination flowed straight through the API's source-of-truth
validation into the query layer instead of failing with a clean 400:
- ListMemoriesQuerySchema guards its string branch with /^\d+$/ (which
still admits "0"), but the z.number() branch accepted any number:
{ page: -1, limit: -5 } and fractional values like 2.5 parsed
successfully; only limit > 1100 was rejected
- DocumentsWithMemoriesQuerySchema (the input schema for
POST /documents/documents) had bare z.number() for both page and
limit with no bounds at all
Require page and limit to be positive integers in both schemas. The
1100 limit cap and all defaults are unchanged, and no new upper bound
is introduced for the documents schema since existing web flows
legitimately request large pages.
Covered with bun tests: defaults, numeric and numeric-string
acceptance, the 1100 cap, and rejection of zero/negative/fractional
values on both schemas.
|
||
|---|---|---|
| .. | ||
| agent-framework-python | ||
| ai-sdk | ||
| cartesia-sdk-python | ||
| docs-test | ||
| hooks | ||
| lib | ||
| memory-graph | ||
| openai-sdk-python | ||
| pipecat-sdk-python | ||
| tools | ||
| ui | ||
| validation | ||