Swift 5 compatibility (and enum exhaustive check timeout) #87 #88
Conversation
Hello @mitchins, When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es). The commits that are missing a linked GitHub account are the following:
Unfortunately, we are unable to accept this pull request until this situation is corrected. Here are your options:
We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community. Thanks, I look forward to checking this PR again soon! ❤️ |
Looks like we have a credential issue on Travis?
@robbiet480 any clue if we need to house-keep this? |
@mitchins Travis has been broken for a while now, so no worries there. PR looks good, thanks for this! |
Resolves #87
Added a default case handler, and because the return type is not optional and we cannot throw inside a computed var it just does fatalError() with a message of where.
Assuming we never had this before and it IS exhaustive, the compiler just doesn't know it - it won't be an issue.
Bumped swift to 5.0 without any other changes to remove compiler warning.
Perhaps @robbiet480 is suitable reviewer?
Edit: This has been tested with a clean branch install and generates without issue or compiler warning in Xcode 11.3 and cocoa pods 1.8.4