You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "James E. King III (JIRA)" <ji...@apache.org> on 2019/01/26 14:46:00 UTC

[jira] [Commented] (THRIFT-79) Thrift::TransportException should have specific subclasses for error types instead of the "type" accesor

    [ https://issues.apache.org/jira/browse/THRIFT-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753097#comment-16753097 ] 

James E. King III commented on THRIFT-79:
-----------------------------------------

It would be nice to do this in many languages.

> Thrift::TransportException should have specific subclasses for error types instead of the "type" accesor
> --------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-79
>                 URL: https://issues.apache.org/jira/browse/THRIFT-79
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Ruby - Library
>            Reporter: Bryan Duxbury
>            Priority: Minor
>
> The "type" attribute of Thrift::TransportException seems rather awkward. The idiom in a lot of languages, Ruby included, is to make subclasses for each exception type. I think we should switch to subclasses in Ruby.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)