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
thekaveman opened this issue
Apr 29, 2024
· 0 comments
Labels
back-endDjango views, sessions, middleware, models, migrations etc.choreChores and tasks for code cleanup, dev experience, admin/configuration settings, etc.
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
EligibilityVerifier.start_template stores its default value on the model
back-endDjango views, sessions, middleware, models, migrations etc.choreChores and tasks for code cleanup, dev experience, admin/configuration settings, etc.
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
EligibilityVerifier.start_template
stores its default value on the modeleligibility.views.TEMPLATE_START
is removedAdditional context
The same approach is being taken in #2053
The text was updated successfully, but these errors were encountered: