-
Notifications
You must be signed in to change notification settings - Fork 208
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-1426: Modals should not be extensions #961
Conversation
Size Change: -330 kB (-9%) ✅ Total Size: 3.21 MB
ℹ️ View Unchanged
|
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.
LGTM. Excellent addition, @brandones!
Excellent! Thanks @brandones! |
Could we write up some docs on this to the O3 docs site, @brandones. Also, should the ticket cover all the places that need to be refactored? |
Yeah, I will write some docs! About the ticket, sure, fair enough, I can take care of the refactoring. Though it would be a fine beginner ticket if that would be useful. |
Requirements
feat
,fix
, orchore
, among others). See existing PR titles for inspiration.For changes to apps
If applicable
Summary
This creates a new "modal system" specifically for modals. Apps should move modals out of the "extensions" section of
routes.json
and into the "modals" section. The modals system is much simpler than the extension system. Modals defined as extensions are supported for backwards compatibility, but a console warning is logged.There should be no UI change associated with this change.
Screenshots
modals.mp4
Related Issue
https://issues.openmrs.org/browse/O3-1426
Other
Requires routes JSON Schema update. PR: openmrs/openmrs-contrib-json-schemas#6