[
https://issues.apache.org/jira/browse/THRIFT-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157856#comment-14157856
]
ASF GitHub Bot commented on THRIFT-809:
---------------------------------------
Github user henrique commented on the pull request:
https://github.com/apache/thrift/pull/232#issuecomment-57777787
Please check https://travis-ci.org/apache/thrift/jobs/36811962#L4284
I think it's just a namespace problem.
Cheers!
> 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
>
> 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)
