Skip to content

fix: add upper bound validation for spot history --limit - #27

Open
MayurK-cmd wants to merge 1 commit into
jup-ag:mainfrom
MayurK-cmd:fix/spot-history-limit-validation
Open

fix: add upper bound validation for spot history --limit#27
MayurK-cmd wants to merge 1 commit into
jup-ag:mainfrom
MayurK-cmd:fix/spot-history-limit-validation

Conversation

@MayurK-cmd

Copy link
Copy Markdown

Fixes #22

The spot history command now validates that --limit is between 1 and 15, matching the API's maximum allowed value. Previously, users could pass --limit 1000 which would fail silently at the API level.

Changes:

  • Add limit > 15 check in SpotCommand.history()
  • Throw clear error: '--limit must be between 1 and 15'
  • Add4 e2e tests validating bounds (reject >15, 0, negative; accept 1-15)

The spot history command now validates that --limit is between 1 and 15,
matching the API's maximum allowed value. Previously, users could pass
--limit 1000 which would fail silently at the API level.

Changes:
- Add limit > 15 check in SpotCommand.history()
- Throw clear error: '--limit must be between 1 and 15'
- Add4 e2e tests validating bounds (reject >15, 0, negative; accept 1-15)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing upper bound validation for --limit in spot history

1 participant