swift - CoreData: Not null property should be optional? -

I'm not sure about Swift and CoreData's best practice Do you think that zero property is not basically alternative needed?

For example

  import import imports imported CoreData class item: NSManagedObject {@NSManaged var itemId: String // Not null property @NSManaged var itemPrice: string? // tap is possible}  

I wonder if I should inform other programmers who do not have the property or not.

I would like to know what you do generally, do this question based on an opinion but I am sure how to deal with alternative is useful for others.

FYI got me the same question

>

.. It is clearly mentioned - you can specify that one attribute is optional - that is, the value is not required. In general, however, you become frustrated by doing this - especially for numerical values ​​(usually you can get better results by using mandatory properties with basic values ​​- in model 0)

< / Div>