Summary: The problem is that `Models.is_field_nonnullable` didn't differentiate between - having a nullable model (in which case we want the field to be NULLABLE), - not having a model at all (in which case we want the field to be THIRDPARTY_NONNULL). The problem was noticed only now because previously we didn't have any NULLABLE field models. Reviewed By: ngorogiannis Differential Revision: D27709508 fbshipit-source-id: b98c8f86fmaster
parent
341169ff0f
commit
a2bc973125
Loading…
Reference in new issue