Repository navigation
Prepare 0.2.0: use structured hierarchical paths - #41
Merged
Merged
Conversation
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.
Hierarchical path strings can resolve to the wrong object when exact names contain dots, brackets or other punctuation. Replace them throughout the API and MCP tools with lists of exact names and a separate
bitfield. For example,["a.b"]selects one instance while["a", "b"]selects a different occurrence.This is a breaking client change: string paths are rejected without a compatibility parser. Search patterns use per-element globs with
**for recursive descent. Returned descriptors round-trip throughresolve; connectivity, cone groups, intent, hierarchy, source and schematic tools use the structured contract, including typed nested export and annotation schemas.Prepare version 0.2.0, update runtime/MCP Registry metadata, convert examples and tests, and add release notes, a changelog and migration documentation. No tag or package publication is included.
Validation:
git diff --checkpasses.twine check.CVA6 remains pinned to v5.3.0. Upstream release, master revision and issue #3594 were rechecked and are unchanged from the prior 0.7.35 validation.