-
Notifications
You must be signed in to change notification settings - Fork 121
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
Add support for 'anyxml' element - seen in ietf-netconf.yang rpc model #284
Comments
Hi eduardpo, Reproducing your issue is key to understand it and fix it. I looked for a fresh version of ietf-netconf.yang and found https://yangcatalog.org/yang-search/module_details/ietf-netconf With this model, there seems to be no issues: pyang --plugindir $PYBINDPLUGIN -f pybind -o outputs/binding.py models/[email protected] How are you calling pyang and pyangbind from pyang-binder? An equivalent call to pyang works? Looking forward to helping you with the issue. |
Hi eduardpo, My bad, I missed the title of the issue, stating that you use '--build-rpc' option. Then I have the same error as you reported. 'pyang --build-rpcs' would ' Generate class bindings for the input and output of RPCs defined in each module. These are placed at the root of each module'. I have first need to understand this to track and identify the Exception you reported. |
I think the problem is that pyangbind expects the childless elements to have a 'type' defined, but 'anyxml' and 'anydata' do not have it. Checking for the presence of 'type' before trying to build the element would fix this. |
I was reading https://www.rfc-editor.org/rfc/rfc6020.html#section-7.10, and it seems this Issue is about implementing the 'anyxml' statement. |
Hi,
Is it a normal behavior?
Thanks,
Ed
The text was updated successfully, but these errors were encountered: