fix: add ALL , ONE_MONTH intervals to PriceHistoryInterval#58
fix: add ALL , ONE_MONTH intervals to PriceHistoryInterval#58arpitBhalla wants to merge 1 commit intoPolymarket:mainfrom
ALL , ONE_MONTH intervals to PriceHistoryInterval#58Conversation
Added new intervals for price history.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7f823af. Configure here.
| export enum PriceHistoryInterval { | ||
| MAX = "max", | ||
| ALL = "all", | ||
| ONE_MONTH = "1m", |
There was a problem hiding this comment.
Enum name ONE_MONTH is wrong for "1m" value
High Severity
The ONE_MONTH enum member maps to "1m", but according to the Polymarket API documentation, "1m" represents 1 minute, not 1 month. The available intervals are 1m (1 minute), 1h (1 hour), 6h (6 hours), 1d (1 day), 1w (1 week), all, and max. The enum name will mislead consumers into thinking they're requesting one month of data when they're actually requesting one-minute granularity.
Reviewed by Cursor Bugbot for commit 7f823af. Configure here.


Added missing intervals for price history.
Note
Low Risk
Low risk type-only change that expands
PriceHistoryInterval; main impact is downstream code may start sending/handling the new interval values.Overview
Updates
PriceHistoryIntervalinsrc/types/clob.tsto include the missingALL("all") andONE_MONTH("1m") options, with a reference link to the API docs.Reviewed by Cursor Bugbot for commit 7f823af. Bugbot is set up for automated code reviews on this repo. Configure here.