You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2022. It is now read-only.
If you are not a member of this project, skip this step
How do the users test this change?
Log in (as at least an editor).
Go to the agents view.
Choose a table row and click on the set translation button.
Choose and click on a language in the popover.
Confirm that the language code for the selected language shows in the browser window (It will likely be something like http://localhost:4200/content/set-translation/1/en-US).
Try changing the language code value to something invalid: (http://localhost:4200/content/set-translation/1/test).
Confirm that the app returns to the agent view.
Confirm that it shows a notification message when it doesn't get a valid language code.
Confirm that the notification messages translate into the active language.
The text was updated successfully, but these errors were encountered:
Desired Use Case
The webapp should only load routes with the
:languageCode
route parameter when the parameter is one of the supported language codes.Actual/Current Behavior
The feature is not yet implemented.
Steps to Implement This Feature
isAvailableLanguageCode()
service method.HasValidLanguageGuard
.Pre-Testing TODOs
What needs to be done before testing.
set-translate
route. To test it now, add the following to the content routing module:Testing Steps
If you are not a member of this project, skip this step
How do the users test this change?
http://localhost:4200/content/set-translation/1/en-US
).http://localhost:4200/content/set-translation/1/test
).The text was updated successfully, but these errors were encountered: