Comments (7)
@lalver1 yes you are absolutely right -- since that attribute is calculated from the others that are moving, it should be moved too.
And it looks like the same goes for ClaimsProvider.client_id
which is calculating from ClaimsProvider.client_id_secret_name
which is also moving.
Remember the ultimate goal here is #2236 where all the details relevant to the specific flow are going to be on the EnrollmentFlow
model. So that will include these fields/attributes we're discussing here.
from benefits.
Perfect, I'll edit the acceptance criteria whenever it is helpful to track these changes, thanks!
from benefits.
@lalver1 when you have a branch with a migration file, can you push that up please? I want to start #2282 from your work.
from benefits.
Thanks @thekaveman , yep I was wondering about that second part so that makes sense that client_id_secret_name
is not moving.
In case it helps, I created a draft PR with the first part of this refactor, moving scope
and claim
from ClaimsProvider
to EligibilityVerifier
. But the migration file is not finished since I'm missing the parts below. You'll see comments in parts of the code I am still working on:
scope
andclaim
data migration ✅- admin permissions update
- add
EligibilityVerifier.claims_scheme
as optional (leave as required onClaimsProvider
) ✅ - updating tests ✅
- updating documentation
from benefits.
@thekaveman , would it also make sense to add
-
ClaimsProvider.supports_claims_verification
moved toEligibilityVerifier.supports_claims_verification
to the acceptance criteria since it is a model attribute (managed, but I guess still technically an attribute)? Also, since scope
and claim
have been moved to EligibilityVerifier
, it seems that supports_claims_verification
should also move to EligibilityVerifier
?
If not, I think it is possible to keep ClaimsProvider.supports_claims_verification
by adding a eligibility_verifiers = models.OneToOneField("EligibilityVerifier", null=True, on_delete=models.CASCADE)
attribute to ClaimsProvider
(or something similar to get scope
and claim
from EligibilityVerifier
) but I have a feeling this is not too logical since scope
and claim
have been moved to EligibilityVerifier
and the better solution is the one described above?
from benefits.
@lalver1 I was partially wrong here, sorry about that:
@lalver1 yes you are absolutely right -- since that attribute is calculated from the others that are moving, it should be moved too.
And it looks like the same goes for
ClaimsProvider.client_id
which is calculating fromClaimsProvider.client_id_secret_name
which is also moving.Remember the ultimate goal here is #2236 where all the details relevant to the specific flow are going to be on the
EnrollmentFlow
model. So that will include these fields/attributes we're discussing here.
This is wrong:
And it looks like the same goes for
ClaimsProvider.client_id
which is calculating fromClaimsProvider.client_id_secret_name
which is also moving.
client_id_secret_name
is not moving.
from benefits.
Quick update on this ticket @thekaveman, the draft PR is almost ready for a review. I still need to update:
- model fixtures
- documentation
- take one more look at the admin permissions update. Since
scheme
is still inClaimsProvider
the scheme read only field will not change but I think I need to setEligibilityVerifier.claims_scheme
as another read only field in the admin permissions.
from benefits.
Related Issues (20)
- Visual regression: Agency card form padding on Mobile
- Receive "Authority to operate" (ATO) for Calfresh Confirm API HOT 2
- Transit agency staff should access configuration for only their transit agency
- Configure file association in VS Code for `.pages` files
- Model refactor: rename `EligibilityVerifier` to `EnrollmentFlow`
- Model refactor: move `EligibilityType` fields to `EnrollmentFlow`
- Set up URLs for in-person enrollment pages
- Model refactor: move `ClaimsProvider` fields to `EnrollmentFlow` HOT 1
- Model refactor: update `TransitAgency` with `EnrollmentFlow` HOT 1
- Enhance `EnrollmentFlow` model with field to indicate it is a pathway that can only be done in-person HOT 1
- Bug: Visual regression - Eligibility Index - Paragraph not centered HOT 1
- Complete "Authority to operate" (ATO) for Blue Button API HOT 1
- Complete "Authority to operate" (ATO) for Veteran Service History and Eligibility API HOT 1
- Set up file structure for in-person enrollment code (views, templates, forms)
- Add separate view for Django login HOT 1
- Chore: update route for re-enrollment error
- Release model refactors, spacing fixes to explanatory text, incremental Admin improvements HOT 2
- [DESIGN] Medicare cardholder enrollment pathway
- Chore: use `settings` fixture in unit test `test_pre_login_user_add_staff_to_group`
- Chore: refactor unit tests of AdminSite view functions
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from benefits.