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

Track EligibilityVerifier in user session #321

Closed
7 tasks done
Tracked by #317
thekaveman opened this issue Mar 16, 2022 · 0 comments · Fixed by #330
Closed
7 tasks done
Tracked by #317

Track EligibilityVerifier in user session #321

thekaveman opened this issue Mar 16, 2022 · 0 comments · Fixed by #330
Assignees

Comments

@thekaveman
Copy link
Member

thekaveman commented Mar 16, 2022

Background

As part of #317 the application will need maintain the user's selected EligibilityVerifier.

We can do this using the existing session framework which keeps everything local to the user in secure cookies.

Tasks

  • Add a new key _VERIFIER = "verifier" for use elsewhere
  • Create a new function verifier() that uses the key to get the EligibilityVerifier instance corresponding to the saved value from the session; see agency() and eligibility() as examples
  • Update the update() function to accept a new kwarg verifier=None; if not None and it is a valid EligibilityVerifier instance, store the id in the request's session using the key
  • Update the reset() function to also clear the verifier
  • Update the context_dict() function to add the new key/value - this shows up in the debug bar
  • Store the agency's first verifier in session (for now) when an agency is configured
  • Retrieve the verifier from session to give to the API client
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants