fix(l10n): do not call addTranslation without translation #1111
Conversation
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
This was referenced Jul 12, 2025
susnux
approved these changes
Jul 12, 2025
max-nextcloud
force-pushed
the
fix/with-l10n-1.3.4
branch
from
ec2b220 to
36f8ece
Compare
There is no translation for the `en` locale. Use the string `seconds` directly. Signed-off-by: Max <[email protected]>
max-nextcloud
force-pushed
the
fix/with-l10n-1.3.4
branch
from
36f8ece to
fe4397e
Compare
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.
There is no translation for the
enlocale.Use the string
secondsdirectly.Fixes nextcloud-libraries/nextcloud-l10n#957