-
-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(lang): UI string edits, round 2 #1202
Conversation
179f405
to
e5ddc21
Compare
5f63f3a
to
93c28c6
Compare
@@ -24,29 +27,27 @@ const messages = defineMessages({ | |||
applicationTitle: 'Application Title', | |||
applicationurl: 'Application URL', | |||
region: 'Discover Region', | |||
regionTip: | |||
'Filter content by region (only applies to the "Popular" and "Upcoming" categories)', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these tips no longer relevant?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't remove the tip, just the parts in parentheses. We are also filtering results for genres now, and possibly more areas in the future. We can't possibly list them all, and I think we only filter where it makes sense, so I didn't feel the category clarification was necessary anymore.
I did change the region tip to say "filter content by regional availability" though, since that is a bit more clear on what the region setting actually does.
73c1d61
to
c90feb8
Compare
This comment has been minimized.
This comment has been minimized.
c90feb8
to
756d9a0
Compare
馃帀 This PR is included in version 1.22.0 馃帀 The release is available on:
Your semantic-release bot 馃摝馃殌 |
Description
More language string fixes, for things I didn't catch the last time or which were introduced since that first round of string edits. Apologies @sct and translators 馃憖
Also in this PR:
Yup
validation on port number fields to not show errors like "port must be anumber
type, but the final value was:NaN
(cast from the value...
)."FormattedMessage
andFormattedNumber
ReactMarkdown
forReactMarkdownWithHtml
so that images defined using HTMLimg
tags in release notes get displayed properlyScreenshot (if UI-related)
To-Dos
yarn build
yarn i18n:extract
Issues Fixed or Closed
N/A