chore: add new string for translations #553
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
| key: "cph-theme-error-boundary.go-to-homepage" | ||
| title: "Error state go to the homepage link" | ||
| screenshot: "https://drive.google.com/file/d/1rJ9c4mW0YWnL5d6KWWZaY9TJBEH5otLL/view?usp=drive_link" | ||
| value: "Go to the homepage" |
There was a problem hiding this comment.
(nitpick) As mentioned in the other PR, we usually add a newline at the end of the files. To keep everything consistent we should do it here as well.
BrunoBFerreira
approved these changes
Dec 11, 2024
gosiexon-zen
force-pushed
the
mbien/new-translation-strings
branch
from
315cd86 to
6fa919d
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.
Description
Added ErrorBoundary component with default error screen so we need translations for it.
Screenshots
Checklist