Repository navigation
Keep numeric filing search labels and court codes as text - #283
Merged
Merged
Conversation
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.
SQLite JSON lookups can decode numeric-looking catalog names, such as the case type "97", as numbers. Grouped filing searches then fail when processing labels or return numeric court codes where text is expected.
Convert extracted filing, category, and case-type labels and court codes/names to strings, and bump the grouped-results cache version. Add a regression test covering numeric case-type names and court codes/names.
Validation: all 101 filing-search tests passed; the full Python and JavaScript suites passed through the pre-push hooks. Formatting, Ruff, type checking, Bandit, and the migration check also passed.