Weblate: Incremental fetching of changes doesn't seem to work

[valeriocos]

Describe the bug

I tried to fetch changes from a given date without success.

• Side comment 1: the next url returned by the response contain the param timestamp_after (see image below). I understand that this param should be used only to get the first page, the next pages shouldn't include it.

• Side comment 2: by looking at the documentation I see that this has been implemented only for the endpoint api/changes. However, the feature request at https://github.com/WeblateOrg/weblate/issues/3658 was about to support the incremental fetching for a given project (e.g., https://translations.documentfoundation.org/api/projects/libo_help-6-3/changes/?timestamp_after=2020-01-01T00%3A00%3A00%2B00%3A00). I don't know if this decision is a misunderstanding or not.

To Reproduce

Steps to reproduce the behavior:

1. Go to https://translations.documentfoundation.org/api/changes/?timestamp_after=2020-01-01T00%3A00%3A00%2B00%3A00
2. Check that the results returned contain a date prior to 2020-01-01

Expected behavior

Only the changes after a given date should be returned

Screenshots

[nijel]

https://github.com/WeblateOrg/weblate/issues/3658 was implemented in Weblate 4.1, but https://translations.documentfoundation.org/ runs Weblate 3.10.3, so it's expected that it ignores this parameter.

[valeriocos]

thank you for the quick reply @nijel . Do you know a weblate instance where this feature is already deployed?

[nijel]

On the other side, you seem to be correct that it won't work on the project changes endpoint...

It's already deployed on https://hosted.weblate.org/ or https://translate.fedoraproject.org/

[github-actions[bot]]

Thank you for your report, the issue you have reported has just been fixed.

• In case you see a problem with the fix, please comment on this issue.
• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, consider supporting Weblate by donating.

[nijel]

https://hosted.weblate.org/ now has deployed fixed API