-
Notifications
You must be signed in to change notification settings - Fork 71
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
Ruby 2.3 Support #14
Comments
@rubyjedi any estimation when it might be fixed? |
I have no hard date to provide at this time, but would like to squeeze in enough time to bring Soap4R up to current Ruby standards by end of January 2018, give or take 2 weeks. |
Well, that's more than enough for me. Thanks! |
@rubyjedi how is it going? Can we expect Ruby 2.3 support in the nearest feature (1-2 weeks)? |
Support through 2.5 is being worked on as time permits. 'Good news is there's little breakage going from 2.0 up to 2.5. The testing issues are mostly from the new marshalled representations not matching up with what the suites were originally hard-coded to expect. Furthermore, from what I see in Ruby's source code, the marshalling test suite hasn't changed since 2.3 - which means once 2.5 is fully supported, nothing extra should need to be done to back-port to 2.3. A couple of weeks is definitely within the ballpark; if I don't have something out by then, and you've got a project that's blocked waiting on soap4r, ping in this thread to bump it back on my priority list. Thanks! |
Hi! Any updates? |
Add the necessary tweaks to Marshalling code to get Soap4R-ng compatible with Ruby 2.3.
The text was updated successfully, but these errors were encountered: