Fix leading-digit searchphrase breaking award-compliance Vandalizer import#39
Merged
Merged
Conversation
…mport The uniform_guidance_applicability searchphrase began with "2 CFR 200". Vandalizer derives extraction field names by slugifying the searchphrase and prepends an underscore to digit-leading names, which its own field-name validator then rejects on import. Reworded to "Uniform Guidance (2 CFR 200) applicability details." and bumped the workflow to v0.1.1; the extraction contract is unchanged. Regenerated the Vandalizer export and component catalog from the authored manifest. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Summary
uniform_guidance_applicabilitysearchphrase in theaward-compliance-extractionworkflow began with2 CFR 200. Vandalizer derives each extraction field name by slugifying the searchphrase and prepends an underscore to digit-leading names, which its own field-name validator then rejects on import (Fields must not use names with leading underscores).Uniform Guidance (2 CFR 200) applicability details.so the derived name starts with a letter. Bumped the workflow to v0.1.1; the extraction contract is unchanged.award-compliance-extraction.vandalizer.jsonandcomponent_catalog.jsonfrom the authored manifest.Test plan
build_vandalizer_workflows.py,build_component_catalog.py,lint_components.py,build_docs.py, andmkdocs build --strictall pass locallyworkflows/award-compliance-extraction/award-compliance-extraction.vandalizer.jsonto Vandalizer and confirm it imports without the leading-underscore error🤖 Generated with Claude Code