Closed nashysolutions closed 3 years ago
@nashysolutions what's the actual issue? You can use @Field
with optional fields but since there's a lot more going on that just ExpressibleByNilLiteral
(like custom encoding and decoding for the database layer) you should use @OptionalField
There is a hack in the code which is highlighted via some annotation. FluentKit > Properties > Field.swift > line 124 Creating issue for visibility.
Great article here for using 'ExpressibleByNilLiteral' to handle optionals in property wrappers.