[jira] [Resolved] (PROTON-322) Extend the native Ruby array and hash classes to work with the Data type
[ https://issues.apache.org/jira/browse/PROTON-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved PROTON-322. - Resolution: Fixed Extend the native Ruby array and hash classes to work with the Data type Key: PROTON-322 URL: https://issues.apache.org/jira/browse/PROTON-322 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.5 Currently Ruby developers have to explicitly create instances of either Qpid::Proton::Data::List, Qpid::Proton::Data::Array or Qpid::Proton::Data::Map to get access to helper methods for interaction with Qpid::Proton::Data. But this too tightly couples the user to Proton-specific code for non-messaging related functions. Instead, we should leverage Ruby metaprogramming and add the needed functions to the standard Ruby classes directly. That way developers wouldn't need to refactor existing code to work with Proton. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (PROTON-322) Extend the native Ruby array and hash classes to work with the Data type
[ https://issues.apache.org/jira/browse/PROTON-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved PROTON-322. - Resolution: Fixed Fix Version/s: 0.5 Extend the native Ruby array and hash classes to work with the Data type Key: PROTON-322 URL: https://issues.apache.org/jira/browse/PROTON-322 Project: Qpid Proton Issue Type: Improvement Components: proton-c Reporter: Darryl L. Pierce Assignee: Darryl L. Pierce Fix For: 0.5 Currently Ruby developers have to explicitly create instances of either Qpid::Proton::Data::List, Qpid::Proton::Data::Array or Qpid::Proton::Data::Map to get access to helper methods for interaction with Qpid::Proton::Data. But this too tightly couples the user to Proton-specific code for non-messaging related functions. Instead, we should leverage Ruby metaprogramming and add the needed functions to the standard Ruby classes directly. That way developers wouldn't need to refactor existing code to work with Proton. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
