This repository was archived by the owner on Jan 17, 2019. It is now read-only.
Open
Conversation
Contributor
|
... but if we do create a protocol for the VC (there are still other cases where it's easier if it's a concrete class), we'd want to expose this in the API as I think we should get to a point where we're not experimenting so much with different VC implementations and then look at whether using a protocol in the API is feasible. For now, let's keep it as it is. |
Generated by 🚫 Danger |
Contributor
|
@marmelroy @cerihughes With Swift 4 it’ll be possible to expose and use types as |
Contributor
Author
|
@rastersize, can't wait :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@cerihughes and I discussed the fact that subclassing HubViewController in order to define a contract (i.e. act as a protocol) was a bit strange.
The argument against it was that Swift will look at UIViewController as just a UIViewController and there will be lots of casting in the Swift code.
That's true (for now).
However, Swift looks at id as a HubViewController protocol.
Going with this approach, there's only one line of casting in the Swift code and that's only to make UIKit happy. I think that's acceptable.