-
Notifications
You must be signed in to change notification settings - Fork 248
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
(feat) O3-3818: Extend clinical forms workspace #2017
Conversation
Size Change: +79 B (0%) Total Size: 14.8 MB ℹ️ View Unchanged
|
This PR depends on this PR #2018 |
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 @usamaidrsk ! Defer to others on this one.
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.
Looks good to me, but I think others with more knowledge of the workspace should review.
ebea026
to
23838da
Compare
Okay so it looks like the deeper problem this is trying to mitigate is that really we don't want workspaces themselves to have to say whether they are part of a sidebar family or not. That really should be defined by the workspace container. Then we will just be able to reuse the same workspaces from the patient chart in the ward app, without having to do this awkward duplicate definition thing. I have filed O3-4077 to suggest a fix for the workspace system. CC @ibacher @denniskigen @chibongho @vasharma05 , or if someone wants to find me a contract to do it :) |
export const clinicalFormsWorkspaceExtension = getAsyncLifecycle( | ||
() => import('./forms/forms-dashboard.workspace'), | ||
options, | ||
); |
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.
This is a duplicate declaration; it doesn't add anything. The code would be easier to understand if the extension registration simply referred to the clincialFormsWorkspace
object. Then it would be immediately obvious we are doing something weird, rather than taking time to figure out we are doing something weird :)
* (feat) extend clinical forms workspace * (fix) fix failing test
Requirements
Summary
This PR extends clinical forms workspace i.e(to the ward app). This it to eliminate where a user has to go to and fro from the patient chart to the ward app so as to fill forms.
Screenshots
Related Issue
https://openmrs.atlassian.net/browse/O3-3818
Other