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: JS TypeScript extensions (was: enum new feature)
Date Wed, 24 Sep 2014 00:16:23 GMT
here:
https://issues.apache.org/jira/browse/THRIFT-2720

On Tue, Sep 23, 2014 at 7:01 PM, Jens Geyer <jensgeyer@hotmail.com> wrote:

>
> I'd recommend to file a JIRA ticket in that case.
>
>
> -----Urspr√ľngliche Nachricht----- From: Rodolfo Ochoa
> Sent: Wednesday, September 24, 2014 1:12 AM
> To: user
> Subject: Re: JS TypeScript extensions (was: enum new feature)
>
>
> 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 <jensgeyer@hotmail.com> 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 <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*
>>
>>
>
>
> --
> *Rod.O*
>



-- 
*Rod.O*

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