thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodolfo Ochoa <rodolfo.oc...@gmail.com>
Subject Re: enum new feature
Date Tue, 23 Sep 2014 15:30:22 GMT
the issue is on node.js, an enum is generated like this:
ttypes.TPolicy = {
  '1' : 'NO_SYNC',
  'NO_SYNC' : 1,
  '2' : 'SYNC',
  'SYNC' : 2,
  '3' : 'WRITE_NO_SYNC',
  'WRITE_NO_SYNC' : 3
};

correct is:
ttypes.TPolicy = {
  'NO_SYNC' : 1,
  'SYNC' : 2,
  'WRITE_NO_SYNC' : 3
};

unless this is a feature that can be corrected with a flag or something...



On Tue, Sep 23, 2014 at 1:53 AM, Jens Geyer <jensgeyer@hotmail.com> wrote:

> Hi Rodolfo,
>
> what is the exact issue you are facing? You don't have to do it this way.
>
> Have fun,
> JensG
> ________________________________
> Von: Rodolfo Ochoa
> Gesendet: 22.09.2014 22:39
> An: user
> Betreff: enum new feature
>
> there is a "new feature" on current master for node, where the generated
> enums are now bivalent (how you call it?),
> for example:
>
> ttypes.TPolicy = {
>   '1' : 'NO_SYNC',
>   'NO_SYNC' : 1,
>   '2' : 'SYNC',
>   'SYNC' : 2,
>   '3' : 'WRITE_NO_SYNC',
>   'WRITE_NO_SYNC' : 3
> };
>
> how you avoid this? I just want a simple enum:
> ttypes.TPolicy = {
>   'NO_SYNC' : 1,
>   'SYNC' : 2,
>   'WRITE_NO_SYNC' : 3
> };
>
>
>
> --
> *Rod.O*
>



-- 
*Rod.O*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message