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

Enhance EligibilityType model with expiration-related field(s) #1938

Closed
3 tasks done
Tracked by #1878
thekaveman opened this issue Mar 11, 2024 · 0 comments · Fixed by #1957
Closed
3 tasks done
Tracked by #1878

Enhance EligibilityType model with expiration-related field(s) #1938

thekaveman opened this issue Mar 11, 2024 · 0 comments · Fixed by #1957
Assignees
Labels
back-end Django views, sessions, middleware, models, migrations etc.

Comments

@thekaveman
Copy link
Member

thekaveman commented Mar 11, 2024

With the coming Low-income / CalFresh enrollment flow, we'll need a way to display certain information and apply logic in-code for discounts that expire, e.g.

  • Does the discount / eligibility type expire at all?
  • How long after enrollment does the discount expire?
  • How long before expiration can a user re-enroll?

For CalFresh, this will be used in a number of places, e.g.

We need a relatively simple way to make these decisions without (ideally) having to hardcode this logic into the templates / views, and to make this more modular for future, non-CalFresh flows that expire (e.g. students, enhancements to Agency cards).

Acceptance criteria

The following fields are added to the EligibilityType model:

@thekaveman thekaveman added the back-end Django views, sessions, middleware, models, migrations etc. label Mar 11, 2024
@thekaveman thekaveman changed the title Enhance EligibilityType model with a field indicating if expiration is supported Enhance EligibilityType model with expiration-related field(s) Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end Django views, sessions, middleware, models, migrations etc.
Projects
Status: Done
2 participants