-
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
Namespace issue #899
Comments
Also, correct me if I'm wrong, but #857 had a fix for this… |
Seems like #469 might be related too... |
Also in the forum |
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. |
Not sure that's a great way to treat contributions. |
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. |
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. |
The same issue has been reported at least 2 times, and was closed by that stupid bot.
Re-creating an issue because I can't open any of the previous ones.
#820
#895
#862
The text was updated successfully, but these errors were encountered: