fix: loading translations via changed date #44
Merged
Conversation
This file contains 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
When using the units API and getting the translations via `"changed:>=YYYY-MM-DD"` you will not get all translations wanted. Translations which were only once touched get only an added date. So, those translations will not be fetched. This changes query for the `changed` and `added` fields to fix this. Fixes #43
|
Kudos, SonarCloud Quality Gate passed! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When using the units API and getting the translations via
"changed:>=YYYY-MM-DD"you will not get all translations wanted. Translations which were only once touched get only an added date. So, those translations will not be fetched.This changes query for the
changedandaddedfields to fix this.Fixes #43