[
https://issues.apache.org/jira/browse/THRIFT-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjy Weinberger updated THRIFT-1651:
-------------------------------------
Description:
Custom annotations are currently supported on almost all types, but not on
enums (and their values), functions and services. This issue proposes to add
that support, so that all type definitions are uniform in this regard.
This is useful, in particular, in custom code generation off thrift IDLs. For
example, we want to annotate each value in an enum with a "database name" so we
can match it with enum names in our database (which for various reasons are not
the same as the names of the enum values).
was:
Custom annotations are currently supported on almost all types, but not on
enums/senums and their values. This issue proposes to add that support, so that
all type definitions are uniform in this regard.
This is useful, in particular, in custom code generation off thrift IDLs. For
example, we want to annotate each value in an enum with a "database name" so we
can match it with enum names in our database (which for various reasons are not
the same as the names of the enum values).
Summary: Support annotations on all elements (was: Support annotations
on enums/senums and their values)
> Support annotations on all elements
> -----------------------------------
>
> Key: THRIFT-1651
> URL: https://issues.apache.org/jira/browse/THRIFT-1651
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (General)
> Reporter: Benjy Weinberger
> Priority: Minor
> Labels: annotations, compiler, enum
> Attachments: thrift-annotations-on-enums.patch
>
>
> Custom annotations are currently supported on almost all types, but not on
> enums (and their values), functions and services. This issue proposes to add
> that support, so that all type definitions are uniform in this regard.
> This is useful, in particular, in custom code generation off thrift IDLs. For
> example, we want to annotate each value in an enum with a "database name" so
> we can match it with enum names in our database (which for various reasons
> are not the same as the names of the enum values).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
