-
Notifications
You must be signed in to change notification settings - Fork 13
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
two different resumptionTokens? #21
Comments
This is an effect of the implementation, which currently wraps any response type into a single struct. It has not caused too much problems in the past, although I admit, that it could be implemented in a better way. I think the thinking behind the single struct was to just a have a single response type. I leave this issue open as a refactoring reminder. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear,
I notice that in the result xml's were two different resumption tokens:
...</record><resumptionToken completeListSize="56" cursor="" expirationDate=""></resumptionToken></ListRecords><ListSets><resumptionToken completeListSize="" cursor="" expirationDate=""></resumptionToken></ListSets></Response>
It seems, that the empty one under ListSets was added by 'metha-sync' and not in the repository response.
Observe anyone else similar?
Best, Andreas
The text was updated successfully, but these errors were encountered: