-
Notifications
You must be signed in to change notification settings - Fork 9
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: rename EligibilityVerifier
eligibility fields
#2272
Conversation
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
e77ae13
to
7726adb
Compare
fb35314
to
8f0f2a7
Compare
7726adb
to
1bb1ad2
Compare
EligibilityVerifier
eligibility fields
8f0f2a7
to
3941634
Compare
1bb1ad2
to
d8d4be4
Compare
Preview url: https://benefits-2272--cal-itp-previews.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! I also tested an IdG and an eligibility API flow to double check and there were no problems.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The field renaming looks good. Just one thought about the start_template
refactor
da1d8a7
to
686f660
Compare
686f660
to
872fd0c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add eligibility prefix for clarity with forthcoming model refactors
for EligibilityVerifier easier to maintain when optional fields are excluded
model stores the default value
872fd0c
to
8880a3e
Compare
Closes #2063
Closes #2238