#23 Add an optional policy metadata section - #39
Merged
Conversation
Adds an optional metadata object to schema 1.3.0, compiles the DESCRIPTION clause into metadata.description, and adds catalog-level aliases so a renamed strategies field keeps reading its earlier name. Signed-off-by: jzonthemtn <jeff.zemerick@philterd.ai>
This was referenced Sep 2, 2026
Merged
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.
Closes #23.
metadataobject.descriptionis typed; additional keys are allowed so it can grow without a breaking change. The policy root stays strict.DESCRIPTION '<text>'now compiles tometadata.descriptioninstead of only being returned onCompileResult, so a description travels with the policy. All three references emit it;CompileResult.descriptionis unchanged.phileas_strategies_field_aliases, so an engine still reads a strategies array's earlier name.ZIP_CODEuses it forzipCodeFilterStrategy, which schema 1.3.0 renamed.validate_spec.pychecks each alias exists in the schema.Verified:
validate_spec.pypasses; conformance 130/130 on the Java, Python and .NET references; reference suites 106 / 256 / 237.