🐛 Fix i18n warnings #3039
Merged
🐛 Fix i18n warnings #3039
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
strarsis
force-pushed
the
fix-i18n-warnings
branch
from
a09aae0 to
a98e089
Compare
Add singular placeholder.
strarsis
force-pushed
the
fix-i18n-warnings
branch
from
a98e089 to
04d4fce
Compare
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This PR fixes the i18n warnings by adding a missing translators comment and uses a singular placeholder.
For single comments,
Oneis used instead of a number (in acomments titlecontext), which fixes the 2nd i18n warning.Edit: Fixed something and merged commits into one, hence the force-pushes...