Non-nullable model fields #78
Description
Are there any plans to improve non-nullable fields on Models? Right now, if I'm not mistaken, all fields need to be nullable, so the library can construct them. I think that this should probably be changed, so the constructor accepts all fields as named arguments so that we can access required fields without !.