Repository navigation
Resolve live filing matrix choices by their displayed names - #293
Merged
Merged
Conversation
nonprofittechy
changed the title
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
1 participant
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.
Live filing matrix fixtures used provider codes as stable identities. Will County’s Adoption choice now has a different code from the fixture, so the test timed out even though filers could still choose Adoption.
Define courts, case categories, case types, and filing types by their displayed names and resolve current codes at runtime. Matching ignores capitalization, whitespace, and extraction markers, but rejects missing or ambiguous names with a list of available choices. Tests cover code replacement and both failure modes.
For existing cases, verify the court saved on Confirm case instead of interacting with the hidden native select behind Lookup’s guided picker.
Validation: all 85 JavaScript unit tests and lint pass. Read-only live validation resolved all 20 new-case fixtures and both existing-case court names uniquely. Will adoption and Cook municipal browser flows passed through test-EFSP submission using the named fixtures. The broader application matrix reached 15 successful scenarios; six were blocked by missing matching waiver choices and one by existing-case lookup. Those coverage limits are recorded separately.