Repository navigation
feat(federal-register): add the Federal Register documents resource - #68
Merged
Merged
Conversation
`list_federal_register_documents` and `get_federal_register_document` cover `/api/federal_register/`, the rules, proposed rules, notices and presidential documents published since 1994, with all seventeen filters as named parameters and a 44-field `FederalRegisterDocument` schema. The detail route takes the document's `uuid`, since `document_number` alone is not unique. `full_text` is shapeable on the detail method only and stays out of both default shapes. The vendored contract is refreshed to API 5.3.0; the unrelated drift that refresh surfaces (an `agency` filter on three resources and an `organization` expand on four) is baselined as tracked gaps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…5.3.0 `list_budget_accounts`, `list_exclusions` and `list_itdashboard_investments` take an `agency` argument for the API's organization-subtree `agency` filter. The regenerated shape overlay accepts the `organization` expand on budget accounts, exclusions, SBIR topics and SBIR solicitations, and `organization_id` on budget accounts and exclusions. Both baselines drop the gaps this closes, so the 5.3.0 contract is fully covered. The IT Dashboard tier notes now say `agency_name` is available at every plan, matching the API. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Inserting `agency` mid-signature shifted every later positional argument in `list_budget_accounts`, `list_exclusions` and `list_itdashboard_investments`, so an existing positional call would silently send a different filter. Moving it to the end keeps every existing call's meaning unchanged. 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.
What
Adds the Tango API's Federal Register resource (
/api/federal_register/, API 5.3.0): rules, proposed rules, notices and presidential documents published since 1994.list_federal_register_documents()with all seventeen API filters as explicit named parameters:search,document_number,type,agency,fr_agency,publication_date_after/_before,effective_on_after/_before,comments_close_on_after/_before,comments_open,cfr_title,cfr_part,significant,rin,executive_order_number, plusordering.get_federal_register_document(document_uuid)on the detail route, which takes the document'suuid.document_numberalone is not unique, so lookups by number go through the list filter.FederalRegisterDocumentschema (44 fields, all optional) andFEDERAL_REGISTER_MINIMAL/FEDERAL_REGISTER_COMPREHENSIVEdefaults, matching the API's own list and retrieve defaults.full_textis shapeable on the detail method only and is left out of both defaults, since it can run to several MB.create_webhook_alertdocs now listfederal_registeras aquery_type, anddocs/WEBHOOKS.mdlistsalerts.federal_register.match.Other 5.3.0 additions
agencyfilter (organization subtree,|for OR) onlist_budget_accounts(),list_exclusions()andlist_itdashboard_investments().organizationexpand (agency_code,agency_name,department_code,department_name,office_code,office_name,organization_id) is accepted on budget accounts, exclusions, SBIR topics and SBIR solicitations, plusorganization_idon budget accounts and exclusions. These come from regeneratingtango/shapes/generated_overlay.pyagainst the refreshed contract; the regeneration touched only those four resources. Default shapes are unchanged.list_itdashboard_investments()tier notes now match the API:agency_nameandagencyare available at every plan.Contract refresh
The vendored
contracts/filter_shape_contract.jsonis refreshed to API 5.3.0.With the additions above, the SDK covers everything that refresh surfaced:
conformance_baseline.jsonis unchanged frommain, andshape_coverage_baseline.jsononly dropsfederal_register.Testing
uv run pytest: 554 passed, 31 skipped (newtests/test_federal_register.pyandtests/test_organization_scope.py).ruff format --check,ruff check,mypy tango/: clean.check_filter_shape_conformance.py: no errors.check_shape_coverage.py: no new drift.full_textshapes, the threeagencyfilters, and theorganizationexpand on all four resources against the live API.🤖 Generated with Claude Code