Open
Conversation
UweTrottmann
force-pushed
the
collection-assert-pagination
branch
from
b0eef0d to
712caf3
Compare
UweTrottmann
force-pushed
the
collection-assert-pagination
branch
from
03f361e to
67aa8d7
Compare
Owner
Author
|
Actually the user list items do react to different sort orders (if they work, for example title doesn't work if the list contains people). The headers are just not returned as promised. So asserted and documented the quirky behavior: a032b28 |
UweTrottmann
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Can't merge this, yet, as despite being announced in trakt/trakt-api#681
user lists items endpoints don't support sort orders, yetactually works, only headers aren't updated as promisedLast checked: 2026-02-26