Repository navigation
feat(awards): obligations_by_fiscal_year and attachments(extraction_status) (API 5.11.0) - #92
Merged
Merged
Conversation
…tatus) (API 5.11.0)
Contracts, IDVs, OTAs and OTIDVs accept the `obligations_by_fiscal_year(fiscal_year, obligated)` shape expand, parsed as a list of `{fiscal_year: int, obligated: Decimal}`.
It is always `None` on IDVs and OTIDVs, whose transactions report a running lifetime total.
Opportunities and notices accept `attachments(extraction_status)`.
Re-vendors the API contract at 5.11.0 and regenerates the shape overlay.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vdavez
marked this pull request as ready for review
October 19, 2026 17:20
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
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.
What
obligations_by_fiscal_year(fiscal_year, obligated)shape expand onlist_contracts(),list_idvs(),list_otas(),list_otidvs()and theirget_*counterparts (Tango API 5.11.0). Each entry parses asfiscal_year: int,obligated: Decimal. It is alwaysNoneon IDVs and OTIDVs, whose transactions report a running lifetime total.attachments(extraction_status)shape field on opportunities and notices (Tango API 5.11.0).contracts/filter_shape_contract.jsonat 5.11.0 and regeneratedtango/shapes/generated_overlay.py.Notes
explicit_schemas.pyasFiscalYearObligation. The overlay generator also emits an unreferencedObligationsByFiscalYearnested schema with placeholderstrtypes for resources the SDK has no method for. Naming the explicit schema differently keeps the overlay from merging over it.contracts/observed_shape_types.jsonis unchanged; the field is not live yet, so it cannot be probed.Testing
uv run pytest tests/ -m "not integration": 516 passed, 30 skipped.tests/test_obligations_by_fiscal_year.py(20 tests): shapes validate on all four award models, an unknown sub-field is rejected, list responses parseobligatedasDecimal(changing the schema type tostrfails them), IDV/OTIDV null passes through, andattachments(extraction_status)validates on opportunities and notices.uv run mypy tango/: clean.uv run ruff check: clean on every changed file (the remaining findings predate this branch).scripts/check_shape_coverage.py: no new drift.scripts/check_filter_shape_conformance.py: passes.🤖 Generated with Claude Code