Repository navigation
Use "filing code" instead of "filing type" in the interface - #397
Merged
Merged
Conversation
Closes #395 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Refs #395 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Illinois redirects the plans screen to options since #386, which failed the Axe check. Massachusetts still offers plans, so the check uses a separate Massachusetts session (switching jurisdiction signs the shared one out). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #395
Tyler File and Serve uses "filing type" for whether someone is e-filing or serving. It calls the court's document code a "filing code". This is a vocabulary-only swap of user-facing labels, messages and staff screens.
Internal names are unchanged: model fields,
filing_typekeys, extraction and classification keys like"filing type", log lines and code comments. Tests that check the visible wording are updated. The docs indocs/docs/use the same wording (headings, prose, and quoted UI labels); config keys likerules[].filing_typesare unchanged.uv run pytest -q: all passingruff,ty, ESLint on changed JS,node --testunit tests: passingnpm run buildfor the docs: succeeds🤖 Generated with Claude Code