I’m happy to announce that today, ruby_odata has continued to move forward by adding additional features and fixing bugs.
I skipped an update for v0.0.9, so let’s revisit what was added/fixed back then. The major change was support for self-signed SSL certificates. That addition was courtesy of J.D Mullin. I’m sure you remember his contributions back in v0.0.8 when he added Basic HTTP Authentication. Aside from J.D.’s contributions, the library was refactored to only make one call to the service for building classes and collections. Finally, a few bug fixes wrapped up the release.
Now onto v0.0.10. A lot of changes were implemented in this release that ended up allowing for wider support for ruby_odata. Thanks to input from Michael Koegel (@konfusius), Alvaro Tejada (@Blag), Ingo Sauerzapf (@IngoS11), and Juergen Schmerder (@schmerdy) (I apologize if I missed anyone!), ruby_odata now supports (at least basic functionality) for SAP NetWeaver GateWay.
Another big change is the initial support for feed customizations. Properties may not be represented within the
Here’s are the complete list of changes for v0.0.10:
- New Features
- Added the ability to pass additional parameters that are appended to the query string for requests
- Added initial support for feed customizations (SyndicationTitle and SyndicationSummary)
- Enhanced ruby_odata’s awareness of classes based on the metadata instead of relying on results that are returned
- Bug Fixes
- Fixed issues with nested collections (eager loading)
- Handled ArgumentError on the Time.parse for older versions of Ruby; used DateTime.parse instead if Time.parse fails
- Removed the camelize method call when building the root URL for collections (reported by mkoegel, issue #3 on github)
- Handled building results (classes) where the category element is missing but there is a title element instead (reported by mkoegel, issue #3 on github in the comments)
- Change HTTP port to 8989 since 8888 conflicts with the Intel AppStore
- Refactored service step for HTTP calls where the service address is defined within the step making it easier to make changes in the future
For the next release, I hope to continue to fix issues, finally add support for inheritance, add the ability to call a custom WebGet methods added to the service, and hopefully namespacing of entities to limit collisions. Do you have other requests? Add them to the issues list on GitHub. The previous Lighthouse site for issues has been closed in favor of using GitHub.