Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When statement xpath not correctly evaluated within case nodes #46

Open
christian-herber opened this issue Oct 6, 2021 · 0 comments
Open

Comments

@christian-herber
Copy link

According to https://datatracker.ietf.org/doc/html/rfc7950#section-7.21.5

      If the "when" statement is a child of a "uses", "choice", or
      "case" statement, then the context node is the closest ancestor
      node to the node with the "when" statement that is also a data
      node.  If no such node exists, the context node is the root node.
      The accessible tree is tentatively altered during the processing
      of the XPath expression by removing all instances (if any) of the
      nodes added by the "uses", "choice", or "case" statement.

The extension seems to not use the closest ancestor node that is a data node as context node.
For the reference of when to be displayed in the editor, you need to add ../ to the path, which is incorrect. In a correct model, the reference is not shown in the editor.

Originally, I suspected an issue in another tool, and created this ticket: CZ-NIC/yangson#112. Maybe this is helpful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant