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

Refactor eligibility start template default value #2063

Open
3 tasks
thekaveman opened this issue Apr 29, 2024 · 0 comments
Open
3 tasks

Refactor eligibility start template default value #2063

thekaveman opened this issue Apr 29, 2024 · 0 comments
Labels
back-end Django views, sessions, middleware, models, migrations etc. chore Chores and tasks for code cleanup, dev experience, admin/configuration settings, etc.

Comments

@thekaveman
Copy link
Member

thekaveman commented Apr 29, 2024

In #1968 we introduced a new model field to hold a template with a default value that can be overridden if needed. The default was stored directly in the model/database rather than separated as a string in the views.

We decided that this is the best approach for these types of cases, so we need to refactor the existing EligibilityVerifier.start_template to conform to this approach.

Acceptance Criteria

Additional context

The same approach is being taken in #2053

@thekaveman thekaveman added chore Chores and tasks for code cleanup, dev experience, admin/configuration settings, etc. back-end Django views, sessions, middleware, models, migrations etc. labels Apr 29, 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. chore Chores and tasks for code cleanup, dev experience, admin/configuration settings, etc.
Projects
Status: Stretch
Development

No branches or pull requests

1 participant