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

NEW FEATURE | client side routing in embedded applications #1831

Closed
scottqueen-bixal opened this issue Sep 23, 2024 · 3 comments · Fixed by #1834
Closed

NEW FEATURE | client side routing in embedded applications #1831

scottqueen-bixal opened this issue Sep 23, 2024 · 3 comments · Fixed by #1834
Assignees
Labels
V1 Final V1 handoff work
Milestone

Comments

@scottqueen-bixal
Copy link
Collaborator

scottqueen-bixal commented Sep 23, 2024

Implementing a client side browser will come with allow us to access more advanced dynamics in location and state organized views, like;

Acceptance Criteria

  • virtual routes include, /<form-step-heading, /verify-selections, /results, /results/not-eligible
  • handles shared token and its associated selection params
  • when integrated, nginx will handle redirects for unkown child paths to life events, /<life-event/**/*, ie. /death/unknown-path
  • current functionality is expected to work in the same or improved manner
@scottqueen-bixal scottqueen-bixal self-assigned this Sep 23, 2024
@scottqueen-bixal scottqueen-bixal changed the title Discovery | client side routing in embedded applications NEW FEATURE | client side routing in embedded applications Sep 27, 2024
@scottqueen-bixal
Copy link
Collaborator Author

@fongcindy
Copy link
Collaborator

I QA'ed #1473 , nav history through browser back, removal of "back" link, they are all working properly on my end. LGTM

@nickpistone
Copy link
Collaborator

Tested the regular flow and tracking looks normal as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
V1 Final V1 handoff work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants