Clarify JSDoc for orderBy eth_price requirement (addresses #1752) #1774
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.
Motivation
PR #1752 raised concerns about the
orderBy: "eth_price"parameter throwing errors. Rather than removing the parameter documentation as suggested in that PR, this properly clarifies the requirement.Solution
Updated JSDoc comments for both
getOrderandgetOrdersto clearly document that:orderBy: "eth_price", you must also provideasset_contract_addressandtoken_idsparametersTesting
Related
As noted by @ryanio: "The order in which to sort the results. Default: created_date NOTE: If eth_price is used, asset_contract_address and token_id are required."
🤖 Generated with Claude Code
Co-Authored-By: Claude [email protected]