[
https://issues.apache.org/jira/browse/THRIFT-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949288#comment-15949288
]
James E. King, III commented on THRIFT-455:
-------------------------------------------
THRIFT-4126 presents a php implementation change that does required field
validation on serialization and deserialization for the binary protocol. I
started doing a little bit of work on THRIFT-4142 to change the cross and/or
functional tests to verify behavior as well, and I'm concerned about the
general lack of standardization in the area of required field handling, then I
found this ticket. It looks it will take a significant effort to properly
handle required fields.
> Compiler flag to make optional/required field modifiers compulsory
> ------------------------------------------------------------------
>
> Key: THRIFT-455
> URL: https://issues.apache.org/jira/browse/THRIFT-455
> Project: Thrift
> Issue Type: New Feature
> Components: Compiler (General)
> Reporter: Bryan Duxbury
>
> if we are unwilling to globally require users specify "required" or
> "optional" when creating their structs, I think we should at least add a
> command line switch that causes us to enforce that behavior. It would
> certainly make my implementations more reliable, especially when I'm giving
> non-experts the tools to make their own IDLs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
