-
Notifications
You must be signed in to change notification settings - Fork 130
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 20307 flippered Facility Locator Progressive Disclosure #34665
Conversation
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.
ESLint is disabled
vets-website
uses ESLint to help enforce code quality. In most situations we would like ESLint to remain enabled.
What you can do
See if the code can be refactored to avoid disabling ESLint, or wait for a VSP review.
src/applications/facility-locator/components/search-form/service-type/ServicesLoadingOrShow.jsx
Show resolved
Hide resolved
src/applications/facility-locator/components/search-form/service-type/ServicesLoadingOrShow.jsx
Show resolved
Hide resolved
So the geolocation check is probably facing this issue making it "flaky"-ish cypress-io/cypress#2671 Many people seem to have this issue. Unfortunately responses on that thread don't create an opportunity to have a delay in results from getCurrentPosition on the navigator in cypress/electron with the permission aware navigator methods. So we lose the functional test if we use their methods and lose the repeatability/consistency if we use ours. error does not happen in cypress/chrome |
@@ -204,7 +204,8 @@ describe('search query reducer', () => { | |||
type: FETCH_SPECIALTIES_FAILED, | |||
}); | |||
|
|||
expect(state.error).to.eql(true); | |||
expect(state.error).to.eql(true); // can be removed when dependent on the following only |
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.
Not quite clear on the comments here - do we anticipate removing error
when we remove the progressive disclosure flipper?
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.
Yes. Because error
controls the alert in the results section. We have fetchSvcsError with progressive disclosure that is related to the service request/loading
src/applications/facility-locator/tests/e2e/providerSearch.cypress.spec.js
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,321 @@ | |||
import mockFacilitiesSearchResultsV1 from '../../constants/mock-facility-data-v1.json'; |
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.
@eselkin I saw you tagged me for re-review; were you anticipating still making changes to these Cypress files based on the helpers? I can still see quite a few places where we would use that. No worries if not! Just wanted to set my expectations correctly.
@randimays should be good now. The geolocation test still sometimes randomly fails for no good reason. Now passes locally with electron and chrome so not sure what's making it fail on CI. |
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.
ESLint is disabled
vets-website
uses ESLint to help enforce code quality. In most situations we would like ESLint to remain enabled.
What you can do
See if the code can be refactored to avoid disabling ESLint, or wait for a VSP review.
Behind progressive disclosure flipper * Add orientation change on small desktop to FL * Add loading indicator when PPMS/CCP services are loading from external source * Add error message and reset state if error occurs in service request * Only show services selector/typeaheads/etc when requried by facility type * Changed text on PPMS typeahead error pursuant to figma * Added testing helpers for feature toggle interactions
Behind progressive disclosure flipper * Add orientation change on small desktop to FL * Add loading indicator when PPMS/CCP services are loading from external source * Add error message and reset state if error occurs in service request * Only show services selector/typeaheads/etc when requried by facility type * Changed text on PPMS typeahead error pursuant to figma * Added testing helpers for feature toggle interactions
DO NOT MERGE INTO MAIN - this is the base for the integration of changes for FL for staging review
Are you removing, renaming or moving a folder in this PR?
Did you change site-wide styles, platform utilities or other infrastructure?
Summary
Related issue(s)
Testing done
Screenshots
New Small Desktop Display
Before searchAfter search

Small Desktop Display Old
Tablet new (slight changes due to component changes)
Tablet old
Mobile has similar changes to tablet (but button extends on mobile)
Mobile map (new)
Mobile results (new)
Mobile Map (old)
Mobile Results (old)
What areas of the site does it impact?
Affects Facility Locator when flipper `` is on
Acceptance criteria
Quality Assurance & Testing
Error Handling
Authentication
Requested Feedback
Check /find-locations
Check on all viewport sizes
Check for all facility types and representative number of services