-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
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
X-Total-Count missing from new LokaliseApi().keys.list
#53
Comments
Thank you for reporting this, I'll check asap! |
Meanwhile, I would recommend the following approach: const keys = await lokaliseApi.keys.list({
project_id: project_id,
page: 2,
limit: 3,
});
lokaliseApi.keys.totalResults; // => should return total results properly |
Thank you @bodrovis ! |
Okay, so we've discussed this, and for now the above approach is the only available one, but it should work properly for all collections that have pagination data. However, in the near future we'll work on a slightly different approach for obtaining pagination data. This will be a breaking change but nothing too serious. :) |
Please note that this issue is resolved in node SDK v6 which was released a couple of days ago. Now it's possible to fetch |
Thank you @bodrovis 🎉 !! |
Describe the bug
The total count of keys is missing from the response from
new LokaliseApi().keys.list
To Reproduce
Call
new LokaliseApi().keys.list
Expected behavior
Expose
X-Total-Count
to a property in the response fromnew LokaliseApi().keys.list
Your environment:
Additional information:
From this issue we found some headers had been added, but not including
X-Total-Count
CC @ycmjason
The text was updated successfully, but these errors were encountered: