thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (THRIFT-2939) JavaScript generated code for Node and browser is different
Date Sun, 09 Apr 2017 02:23:41 GMT

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

ASF GitHub Bot commented on THRIFT-2939:
----------------------------------------

Github user jeking3 commented on the issue:

    https://github.com/apache/thrift/pull/353
  
    Tag THRIFT-2939 so the PR shows up in github as a linked PR.


> JavaScript generated code for Node and browser is different
> -----------------------------------------------------------
>
>                 Key: THRIFT-2939
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2939
>             Project: Thrift
>          Issue Type: Improvement
>          Components: JavaScript - Compiler, JavaScript - Library
>    Affects Versions: 0.9.2
>            Reporter: Radoslaw Gruchalski
>              Labels: javascript, patch
>
> The generated code for regular JS differs from NodeJS code. NodeJS uses direct return
values from {{read<Type>()}} while regular JS code expects a value from {{read<Type>()}}
to be an object with {{.value}} property.
> This makes it impossible to share generated code between browser JS and NodeJS. The fix
is rather simple:
> - do not append {{.value}} in generated code while accessing values read from protocol
/ transport
> - do not return an object with the value property from {{read}}, return result read
> I am not sure why such difference. Both environment implementations take an input, which
is a protocol, and execute the same read methods. There is no need to have an additional complexity
in regular JS.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message