-
Notifications
You must be signed in to change notification settings - Fork 1
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
[CPDLP-3510] npq internal api revisit fallback for funding eligibility logic in npq #1741
base: main
Are you sure you want to change the base?
[CPDLP-3510] npq internal api revisit fallback for funding eligibility logic in npq #1741
Conversation
228d473
to
48eccdb
Compare
Review app deployed to https://npq-registration-review-1741-web.test.teacherservices.cloud/ |
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.
Thanks @mooktakim is it ok if we only focus on swapping out the feature flag on the funding eligibility section? as there is another ticket to tackle those which will change their location?
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.
All good past Abeer's comment.. also Is the logic behind accepted_applications
and with_targeted_delivery_funding_eligibility
the same as in ECF?
|
||
it "returns nil" do | ||
it ".call returns nil" do |
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.
it "returns nil" do ... ?
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.
those changes reverted now
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.
it was because call
was tested but tsf_data_field_update
wasn't.
Quality Gate passedIssues Measures |
Context
Ticket: https://dfedigital.atlassian.net.mcas.ms/browse/CPDLP-3510
Changes proposed in this pull request
Rails.application.config.npq_separation[:ecf_api_disabled]
flags to useFeature.ecf_api_disabled?
Ecf::NpqProfileUpdater
spec to include one more test