-
Notifications
You must be signed in to change notification settings - Fork 71
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
VACMS-19075: Reduces services to only facility #20417
VACMS-19075: Reduces services to only facility #20417
Conversation
Checking composer.lock changes... |
Checking composer.lock changes... |
Checking composer.lock changes... |
Checking composer.lock changes... |
* - Adds mechanism to define breadcrumbs and pass to page wrapper. - Defines the breadcrumbs for the Form Info page. - Defines the breadcrumbs for the Layout page. * - Adds a template for rendering breadcrumbs. - Includes the breadcrumb template from the page template. - Adds css. * Adds test cases for breadcrumbs. * - Updates breadcrumb strucutre to align with updated designs. - Adds '#content' link to current breadcrumb. - Adds aria-current=page attribute to current breadcrumb list element. * Updates breadcrumb tests to expect updated structure. * Changes url for layout page from '/form-builder/{nid}/layout' to '/form-builder/{nid}'.
Checking composer.lock changes... |
Checking composer.lock changes... |
Cypress Accessibility Violations
|
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.
A couple non-blocking things we could change if we were going to be doing this on (many) other fields in the future:
- Code re-use. Some parts of the 'reduce' and 'ajax' functions could be abstracted to handle different fields in different situations. This would only be beneficial if there were an expectation that we would be doing this in many places.
- Static caching. The '_service_names' functions that return the correct $options for a given facility/system could benefit from static caching if we thought that the editor might be making many changes to the facility/system and needed an extra boost in performance. As it is, this is not worth the effort as the queries are well structured and don't contain joins/other complex requirements.
Nice work!
I checked and review with @omahane, and everything works good from my side. |
Description
Relates to #19075
Testing done
Manually
Screenshots
Facility field after selection
VAMC system health service after AJAX
QA steps
Setup up QA Content Publisher
Create VAMC facility health services
Select Team for PR review
CMS Team
Public websites
Facilities
User support
Accelerated Publishing