Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    I understand the distinction between optional for Core Data and for Swift but I don't understand why a non-optional attribute with a default value is not generated as a non-optional with a default value... It's still a Swift optional. So, how are we supposed to deal with optionals when we know they have a value? (Because non-optional + default value for Core Data). Should we guard ourself in each method that uses the managed object attributes to check if the value is nil or not? Commented Sep 16, 2016 at 1:40
  • I agree, and suggest filing a bug with Apple. For now either (a) change the attribute to be a Swift non-optional or (b) treat it as a Swift optional even though you know there's a value. Neither is ideal, I know. Commented Sep 16, 2016 at 3:23
  • Regarding (a), I'm using Xcode 8 automatic subclass generation for NSManagedObjects. So I don't have any control on the generated temporary class and extension: it's optional by default and can't change that (as far as I understand)... So I'll stick with (b) for now and consider filling a bug with Apple. Commented Sep 16, 2016 at 14:27