We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The default and maximum value when returning token information seems to be shared with these consts here:
cw-nfts/contracts/cw721-base/src/query.rs
Lines 17 to 18 in 27ffdc6
These may be quite low for certain use cases.
If you query tokens you will get something like this:
tokens
nftInfo { tokens: [ '489', '491', '492', '494', '495', '496', '497', '498', '499', '500' ] }
You must pass in the parameters start_after or limit in order to increase this, where the limit is maxed out at 100.
start_after
limit
I feel like both the default and maximum could be increased for queries that return only token IDs.
This might involve separating different constants for various queries that may return larger payloads than just the ID.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The default and maximum value when returning token information seems to be shared with these consts here:
cw-nfts/contracts/cw721-base/src/query.rs
Lines 17 to 18 in 27ffdc6
These may be quite low for certain use cases.
If you query
tokens
you will get something like this:You must pass in the parameters
start_after
orlimit
in order to increase this, where the limit is maxed out at 100.I feel like both the default and maximum could be increased for queries that return only token IDs.
This might involve separating different constants for various queries that may return larger payloads than just the ID.
The text was updated successfully, but these errors were encountered: