-
Notifications
You must be signed in to change notification settings - Fork 616
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
elementFormDefault="qualified" in types regression #916
Comments
Same issue is fixed in #905. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue remains open. |
Given the slow pace of incorporating changes, I've created a gem that patches this issue. All you have to do is include it in your gem 'savon_fixes' You can find the gem here: https://github.com/lukaso/savon_fixes. It currently covers off these issues and PRs: #916, #899, #820, #895, #862, #905 and #549 (they are all duplicates). I haven't yet tested it in anger, but all tests pass, so please feedback if there are any issues. Adaptations of PRs here are also welcome. |
Bug report
Current behavior:
Attributes within a nested type are no longer qualified.
Steps to reproduce current behavior:
Create any document with types with attributes and set
elementFormDefault="qualified"
in WSDL.The attributes in the nested type will not be qualified.
Expected behavior:
Create any nested document with attributes and
elementFormDefault="qualified"
and see that attributes are qualified.See also this example of a properly formatted document: https://www.intertech.com/Blog/xml-schema-elementformdefault-and-attributeformdefault/
System information:
Mac OS Mojave 10.14.6
The bug was introduced in this PR: #676
There is no apparent test coverage of this area of the code. I looked at adding a breaking test to
spec/savon/builder_spec.rb
however not sure how to create nested types for the testThe following test passes without the fix:
I will submit a PR to fix this shortly.
The text was updated successfully, but these errors were encountered: