Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EntryModellable doesn't handle ImplicitOptionals #133

Closed
bennichols opened this issue Sep 29, 2017 · 2 comments · Fixed by #138
Closed

EntryModellable doesn't handle ImplicitOptionals #133

bennichols opened this issue Sep 29, 2017 · 2 comments · Fixed by #138

Comments

@bennichols
Copy link
Contributor

  • contentful.swift version number: 0.9.3
  • Xcode version number: 9.0
  • Target operating system(s) and version number(s)
    - [x ] iOS:
    - [ ] tvOS:
    - [ ] watchOS:
    - [ ] macOS:
  • Package manager:
    - [x ] Carthage
    - [ ] Cocoapods

When I have properties that are required in the CMS, I'd like them to be implicit optionals (end in !) so that I don't have to worry about unwrapping them. Currently anything that is an implicit optional is ignored by then relationshipNames function.

@loudmouth
Copy link
Contributor

Thanks for the reports @bennichols

I'm a bit busy this week but will try to get a fix out as soon as i have capacity.

@loudmouth
Copy link
Contributor

A quick note, as I mentioned in #132 , a new system will be rolled out for decoding entries. Since it will be leveraging the Decodable protocol, you will be able to define your classes however you like. Hang tight in the meantime, and thanks for your patience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants