[
https://issues.apache.org/jira/browse/THRIFT-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14197611#comment-14197611
]
Hudson commented on THRIFT-809:
-------------------------------
SUCCESS: Integrated in Thrift #1331 (See
[https://builds.apache.org/job/Thrift/1331/])
THRIFT-809 Javascript client: Please make required fields actually required.
(roger: rev 25023b16eb4f26d7fcf986e817e8c437e2f08bf3)
* lib/nodejs/lib/thrift/thrift.js
* lib/nodejs/lib/thrift/protocol.js
* compiler/cpp/src/generate/t_js_generator.cc
> Javascript client: Please make required fields actually required.
> ------------------------------------------------------------------
>
> Key: THRIFT-809
> URL: https://issues.apache.org/jira/browse/THRIFT-809
> Project: Thrift
> Issue Type: Improvement
> Components: JavaScript - Compiler
> Reporter: Jordan
> Assignee: Roger Meier
> Fix For: 0.9.2
>
>
> If fields are marked as required then I think that we should be forced to
> supply all of them, even if supplied with null values. Currently, I am able
> to construct an object without all of the required fields, send it to my
> backend, and nowhere does an error occur before sending. This should fail
> fast at the client. Instead, on the server I get null values. Null is so
> different than unspecified.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
