Skip to content
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

Merged
merged 36 commits into from
Feb 26, 2025

Conversation

eselkin
Copy link
Contributor

@eselkin eselkin commented Feb 13, 2025

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?

  • No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
  • Yes, I'm removing, renaming or moving a folder

Did you change site-wide styles, platform utilities or other infrastructure?

Summary

  • Updates FL on small desktop sizes and up to match the new Figma designs
  • Updates to use va-button and other vads components
  • Sitewide team

Related issue(s)

Testing done

  • Updates tests to match new design on desktop

Screenshots

New Small Desktop Display Before search sm-desktop-new

After search
sm-desktop-results-new

Small Desktop Display Old
Tablet new (slight changes due to component changes) tablet-new tablet-results-new
Tablet old tablet-results-old

Mobile has similar changes to tablet (but button extends on mobile)

Mobile map (new) mobile-map-new
Mobile results (new) mobile-results-new
Mobile Map (old) mobile-map-old
Mobile Results (old) mobile-results-old

What areas of the site does it impact?

Affects Facility Locator when flipper `` is on

Acceptance criteria

  1. Check that with flipper on (RI flipper will be on soon) RI shows small desktop

Quality Assurance & Testing

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Linting warnings have been addressed
  • Documentation has been updated (link to documentation *if necessary)
  • Screenshot of the developed feature is added
  • Accessibility testing has been performed

Error Handling

  • Browser console contains no warnings or errors.
  • Events are being sent to the appropriate logging solution
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

  • Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

Check /find-locations
Check on all viewport sizes
Check for all facility types and representative number of services

Copy link

@va-vfs-bot va-vfs-bot left a 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.

@va-vfs-bot va-vfs-bot temporarily deployed to master/VACMS-20307-restore-behavior-add-flag/main February 21, 2025 06:51 Inactive
@eselkin eselkin requested review from randimays and removed request for randimays February 21, 2025 16:23
@eselkin
Copy link
Contributor Author

eselkin commented Feb 21, 2025

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
Copy link
Contributor

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?

Copy link
Contributor Author

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

@@ -0,0 +1,321 @@
import mockFacilitiesSearchResultsV1 from '../../constants/mock-facility-data-v1.json';
Copy link
Contributor

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.

powellkerry
powellkerry previously approved these changes Feb 21, 2025
@va-vfs-bot va-vfs-bot temporarily deployed to master/VACMS-20307-restore-behavior-add-flag/main February 21, 2025 21:05 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/VACMS-20307-restore-behavior-add-flag/main February 24, 2025 21:05 Inactive
@va-vfs-bot va-vfs-bot temporarily deployed to master/VACMS-20307-restore-behavior-add-flag/main February 24, 2025 21:35 Inactive
@eselkin eselkin requested a review from randimays February 24, 2025 21:43
@va-vfs-bot va-vfs-bot temporarily deployed to master/VACMS-20307-restore-behavior-add-flag/main February 25, 2025 20:18 Inactive
@eselkin
Copy link
Contributor Author

eselkin commented Feb 25, 2025

@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.

@va-vfs-bot va-vfs-bot requested a review from a team February 26, 2025 02:24
Copy link

@va-vfs-bot va-vfs-bot left a 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.

@eselkin eselkin merged commit 4bdfc14 into main Feb 26, 2025
83 checks passed
@eselkin eselkin deleted the VACMS-20307-restore-behavior-add-flag branch February 26, 2025 16:59
ConnorJeff pushed a commit that referenced this pull request Mar 3, 2025
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
patrick-brown-oddball pushed a commit that referenced this pull request Mar 4, 2025
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants