feat: update eligibility rules - #152
Merged
Merged
Conversation
mdiapenabc
force-pushed
the
feat/eligibility-rules-update
branch
from
March 18, 2026 07:25
7f55225 to
ddda106
Compare
saifrazabc
approved these changes
Mar 18, 2026
saifrazabc
left a comment
Collaborator
There was a problem hiding this comment.
Approving for update eligibility rules.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
eligible_tbdandnot_eligible_ip_tbdstatuses in outcome stepsWhat Changes
eligible_tbdandnot_eligible_ip_tbdeligible_tbdTOeligible,not_eligible_ip_tbdTOin_payeligible_tbd/not_eligible_ip_tbdTOnot_eligible_out_of_payeligible_tbd/not_eligible_in_pay/not_eligible_ip_tbdTOover_18startDateprior to current month; Ended/Closed fallback checksendDatein previous month; Ended/Closed Non-Placements now route to Step 4 instead of Step 8en-USinstead of 'en-CA' to fixSeptvsSepinconsistency across CLDR versions