well, this feature will introduce A LOT of problems for those who iterate over their enums...
-Rodolfo On Tue, Sep 23, 2014 at 2:36 PM, Jens Geyer <[email protected]> wrote: > Hi Rodolfo, > > the issue is on node.js, an enum is generated like this: >> > > I see. No, seems there is no flag to turn that off. > > The feature has been introduced via the TypeScript extensions, THRIFT-2522 > https://issues.apache.org/jira/browse/THRIFT-2522 > > Can't say much about that. Maybe Henrique or Pascal can chime in. > > > -----Ursprüngliche Nachricht----- From: Rodolfo Ochoa > Sent: Tuesday, September 23, 2014 5:30 PM > To: user > Subject: Re: enum new feature > > 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 <[email protected]> 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* > -- *Rod.O*
