You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, ./xxx is not a valid path identifier. We can add a simple validation logic to augment extension's resolve function to make sure it's compliant. Do you want to give it a try?
yang-module:
After the module is loaded, I loop over every element in the yang instance, no additional node is augmented.
After checking the RFC,
./cont-to-be-aug
does not seem to be a formal node identifier.Maybe an error message is needed?
Even I set the value as a "./123"(a non-existing node), the situation is the same.
The text was updated successfully, but these errors were encountered: