get schema with augmented/prefixed path#229
Open
shrey-gang wants to merge 1 commit intosdcio:mainfrom
Open
Conversation
Author
|
@steiler Please review this change. |
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.
With current implementation if we search for augment/prefixed path as below, the error was thrown in response.
In-oder to search with augmented or prefixed path below changes are made, the breif description of the change
Added support for YANG augment paths in schema resolution. Enhanced getChildren() to include e.Augmented nodes alongside e.Dir children across all path traversal functions (expand.go, object.go, references.go, schema.go, container.go). Refactored persiststore.getSchema() to parse module prefixes (module:name) from path elements, validate first-element prefixes against root modules, and construct database keys using unprefixed names. Augmented modules in non-first path elements (e.g., srl_nokia-ospfv2:ospfv2) now resolve correctly without strict validation, enabling schema lookups for nodes introduced via YANG augment statements.