question regarding node validation with extension plugin

[jeremie6wind]

Hi,
The node callback has been removed from plugin_ext in libyang 4.
In my case, it was used to validate data in a container with extensions.

For example, I have this kind of container:

container cont1 {
   extension myext ;
   list list1 {
     key "name";
     leaf name {
     type string;
   }
   list list2 {
     key "name";
     leaf name {
       type string;
   }
}

The node callback of myext plugin was called and I could check the values of "name" node in both lists.

I could use some must, however if the number of list in cont1 increases, it becomes difficult to maintain.

How should I do that with libyang4?

Thank you.
BR

[michalvasko]

It seems you have misused the callback and extensions so I am not sure we want to make any changes based on such a use-case. I do not remember exactly why have I removed the callback but I think there was no (internal) use for it and I thought the validate() callback functionality can always be extended to all the nodes with extensions, not just the special schema-mount nested data. But like I said, is it really worth it? I do not think this is a good usage of extensions.

[jeremie6wind]

Thank you for your feedback.
This change has a significant impact in term of maintainability and efficiency.
The plugin validation is a lot more efficient than musts.
It would be great if the validate callback could be called with extensions not just the special schema-mount nested data.
Best regards.

[michalvasko]

Fine, the validate callback should now work also the same way the node callback used to work.

[jeremie6wind]

Thank you!