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
We use the Transaction's search API like this:
const txData: Database.ITransactionsPaginated = await this.transactions.search({ senderPublicKey, vendorField });
The problem, that the result's count shows 1 for me for a query I created, but the rows field is empty.
count
rows
Expected Behavior
I expect to get back a result like:
{ "rows": [SOMETHING HERE], "count": 1, "countIsEstimate": true }
Current Behavior
But I get back:
{ "rows": [], "count": 1, "countIsEstimate": true }
Possible Solution
Steps to Reproduce (for bugs)
Context
We are a bridgechain developing a layer2 solution, where we use this API
Your Environment
The text was updated successfully, but these errors were encountered:
Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.
If no reviewer appears after a week, a reminder will be sent out.
Sorry, something went wrong.
Set CORE_API_NO_ESTIMATED_TOTAL_COUNT to true in your .env file.
CORE_API_NO_ESTIMATED_TOTAL_COUNT
true
.env
makes sense! thx for the solution.
This issue has been closed. If you wish to re-open it please provide additional information.
No branches or pull requests
We use the Transaction's search API like this:
The problem, that the result's
count
shows 1 for me for a query I created, but therows
field is empty.Expected Behavior
I expect to get back a result like:
Current Behavior
But I get back:
Possible Solution
Steps to Reproduce (for bugs)
Context
We are a bridgechain developing a layer2 solution, where we use this API
Your Environment
The text was updated successfully, but these errors were encountered: