To this day, there is only a limit (propery configuration) to what's returned.
Remove such limit.
Add pagination following the pagination installed in T605 on /api/1/content/symbol/<expression>/.
Description
Description
Revisions and Commits
Revisions and Commits
| rDWAPPS Web applications | |||
| rDWAPPS5c92533e2731 /api/1/revision/log/: Add pagination explanation | |||
Related Objects
Related Objects
- Mentioned In
- T627: /api/1/revision/origin/log/ - Add pagination
Event Timeline
Comment Actions
To this day, there is only a limit (propery configuration) to what's returned.
Remove such limit.
I don't know the details of that limit, but we might want to keep it too, as safeguard, in addition to pagination. To be discussed…
Add pagination following the pagination installed in T605 on /api/1/content/symbol/<expression>/.
Yes! Ideally, we should have a single implementation of the pagination code, which is easy/trivial to plug into any endpoint that needs it.
Comment Actions
As explained on irc, there is actually a pagination.
The last element is used to create a new /revision/log/ link to follow in the 'next_urls_rev' key.
I tried and improved the docstring instead.