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
[55085] Removes appointment list use of va online scheduling status improvement flag #27685
Conversation
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
… appointment list components Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us> Revert "WIP: skip unit tests" This reverts commit 775c41b. Revert "WIP: enable test" This reverts commit bbb0a30. Revert "WIP: disable test" This reverts commit a32b101. Revert "WIP: test auto push" This reverts commit 3645f01. Revert "WIP: disable test" This reverts commit e0ef1d5.
…-website into ryanshaw/55085-removes-appointment-list-use-of-va_online_scheduling_status_improvement-flag
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
This test was removed because it was used for coverage of the pulldown on the appointment list page which was removed after the vaOnlineSchedulingStatusImprovement feature flag was enabled for all production users Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
…-website into ryanshaw/55085-removes-appointment-list-use-of-va_online_scheduling_status_improvement-flag
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
…-website into ryanshaw/55085-removes-appointment-list-use-of-va_online_scheduling_status_improvement-flag
…-website into ryanshaw/55085-removes-appointment-list-use-of-va_online_scheduling_status_improvement-flag
…-website into ryanshaw/55085-removes-appointment-list-use-of-va_online_scheduling_status_improvement-flag
Signed-off-by: Ryan Shaw <ryan.shaw@adhocteam.us>
…-website into ryanshaw/55085-removes-appointment-list-use-of-va_online_scheduling_status_improvement-flag
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.
to="/" | ||
onClick={() => callback(true)} | ||
aria-current={ | ||
Boolean(isUpcoming).toString() // eslint-disable-next-line jsx-a11y/aria-proptypes |
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 disabled here
}); | ||
}} | ||
aria-current={ | ||
Boolean(isPending).toString() // eslint-disable-next-line jsx-a11y/aria-proptypes |
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 disabled here
}); | ||
}} | ||
aria-current={ | ||
Boolean(isPast).toString() // eslint-disable-next-line jsx-a11y/aria-proptypes |
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 disabled here
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 pretty large pull request. Is there any way this can be broken down into smaller more manageable submissions? If not, then can you provide a broader explanation of how this was tested beyond unit tests and e2e tests? Was this application run locally in browser to verify it functions as expected?
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 pretty large pull request. Is there any way this can be broken down into smaller more manageable submissions? If not, then can you provide a broader explanation of how this was tested beyond unit tests and e2e tests? Was this application run locally in browser to verify it functions as expected?
@micahchiang We don't currently use this feature flag, this removes a lot of conditional code that is no longer used. It has been broken down by higher level directories within the appointments application but I can break it down further. As for testing, manual spot checking of common user flows was done locally.
Closing this PR and addressing the issue with a set of smaller PRs, here's the first one: #28008 |
Summary
This removes the use of the
va_online_scheduling_status_improvement
feature flag from the/src/applications/vaos/appointment-list
component and child components within VA online scheduling. It is part of a set of PR's to address department-of-veterans-affairs/va.gov-team#55085Related issue(s)
department-of-veterans-affairs/va.gov-team#55085
Testing done
Acceptance criteria
Quality Assurance & Testing
Error Handling
Authentication