Add label metadata to example parameters for each fix category #7105
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.
Summary
This PR adds label metadata to example parameters across four categories that were identified as lacking proper labels. These fixes establish patterns for future work to ensure all parameters have human-readable labels.
Motivation: API v2 alpha aims to ensure all parameters have defined labels to improve trust for front-end users. Without proper labels, users see cryptic paths instead of meaningful descriptions.
Changes
gov/states/wi/tax/income/deductions/standard/max.yamllabelgov/irs/credits/education/american_opportunity_credit/amount.yamllabelgov/irs/income/amt/exemption/amount.yamlbreakdown+labelrange()gov/irs/deductions/itemized/salt_and_real_estate/state_sales_tax_table/tax.yamlbreakdown_labelsDocumentation
For detailed explanations of each category, before/after examples, and next steps, please see:
docs/PARAMETER_LABEL_METADATA_IMPROVEMENTS.md
Notes
breakdown_labelsfield is a new metadata field that requires a corresponding update topolicyengine.pyto be fully functional🤖 Generated with Claude Code