You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to update the URL for the travel pay experience before rolling out so that future changes / adding features won't impact the end user and will reduce additional complexity for our team.
Context
Our current URL/entry point is va.gov/my-health/travel-claim-status, however as we add features, the "status" part of the url is misleading. We need to update the base URL to the more generic "travel-pay"; from there we can add specific child routes to the feature application.
Changing the rootUrl for the app entry requires changes in 3 repos: vets-website (manifest.json, and all tests), content-build (registry.json), and vsp-platform-revproxy (react_routes.yml).
Order for merging is vets-website, then content-build then revproxy.
Issue Description
We would like to update the URL for the travel pay experience before rolling out so that future changes / adding features won't impact the end user and will reduce additional complexity for our team.
Context
Our current URL/entry point is
va.gov/my-health/travel-claim-status
, however as we add features, the "status" part of the url is misleading. We need to update the base URL to the more generic "travel-pay"; from there we can add specific child routes to the feature application.Design
Impact
Notes
URL
Current entry point/URL:
va.gov/my-health/travel-claim-status
Desired entry point/URL:
va.gov/my-health/travel-pay/{child routes here}
Front end tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: