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

Hudson commented on THRIFT-2469:
--------------------------------

SUCCESS: Integrated in Thrift #1163 (See 
[https://builds.apache.org/job/Thrift/1163/])
THRIFT-2469 "java:fullcamel" option to automatically camel-case underscored 
attribute names (roger: rev e86428c6b0a278c070038b8c0182ceccc60196d5)
* lib/java/README.md
* compiler/cpp/src/generate/t_java_generator.cc
* test/DenseLinkingTest.thrift
* lib/java/build.xml
THRIFT-2469 "java:fullcamel" option to automatically camel-case underscored 
attribute names (roger: rev 5c976038f9876198de0e4e5fa91029eda0c33264)
* lib/java/test/org/apache/thrift/TestFullCamel.java


> "java:fullcamel" option to automatically camel-case underscored attribute 
> names
> -------------------------------------------------------------------------------
>
>                 Key: THRIFT-2469
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2469
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Java - Compiler
>            Reporter: Tom Lee
>            Assignee: Roger Meier
>            Priority: Minor
>             Fix For: 0.9.2
>
>         Attachments: thrift-2469-fullcamel-option-v1.patch
>
>
> Currently the code generator will generate a getter method called 
> "getFoo_bar" for a Thrift attribute called "foo_bar". This is unfortunate 
> since it's considered "bad style" in Java, but is often unavoidable if you 
> need to share a Thrift IDL with clients of another language (e.g. Ruby, where 
> underscores are the norm).
> The attached patch adds support for a "fullcamel" option that does something 
> resembling the opposite of "nocamel" by uppercasing both the first character 
> in the name as well as any characters that follow an underscore in 
> t_java_generator::get_cap_name. The underscores themselves are completely 
> omitted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to