-
Notifications
You must be signed in to change notification settings - Fork 246
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(fix) O3-4312: Add translation to start visit workspace title #2169
Conversation
Size Change: -155 kB (-0.96%) Total Size: 16.1 MB
ℹ️ View Unchanged
|
4d4e1b3
to
69b4dc1
Compare
@@ -159,6 +159,7 @@ export const genericDashboard = getSyncLifecycle(genericDashboardComponent, { | |||
moduleName, | |||
}); | |||
|
|||
// t('startAVisit', 'Start a visit') |
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.
The key mentioned in the routes.json
file is startVisit
not startAVisit
. Please take of these things.
Let's not try to create a new key, and keep the translations as is.
Thanks!
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.
Thanks @vasharma05 , however the startAVisit
key is also used on the visit header component too here , which is the same key needed as the workspace title "Start a visit".
@@ -159,7 +159,7 @@ export const genericDashboard = getSyncLifecycle(genericDashboardComponent, { | |||
moduleName, | |||
}); | |||
|
|||
// t('startAVisit', 'Start a visit') | |||
// t('startVisit', 'Start visit') |
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.
Thanks @vasharma05 , however this will change the design, from Start a visit
to Start visit
. See here
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.
We should probably change that key to something different altogether. I propose startVisitWorkspaceTitle
to match what we're doing in the orders app. Additionally, and maybe this is beyond the scope of this PR, we should also probably register this workspace using the workspaces key in the routes.json
file.
Registering workspaces using extensions isn't the ideal approach at this point. Using the workspace system has the added benefit of saner handling of things like workspace titles and other metadata.
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.
Much improved. Thanks, @usamaidrsk!
Requirements
Summary
This PR fixed the start visit workspace title to use the
startVisit
translation key.Screenshots
Related Issue
https://openmrs.atlassian.net/browse/O3-4312
Other