You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, for now we have View adopting SpotConfigurable, which confuses, at least for me at first. Because SpotConfigurable involves something that can be configurable on the Spotable object, instead of the View
publicprotocolSpotConfigurable:ItemConfigurable{/// The perferred view size of the view.varpreferredViewSize:CGSize{get}func prepareForReuse()}
The text was updated successfully, but these errors were encountered:
@onmyway133 I totally agree, this is not the best naming. I think we can solve this by moving Item back into Spots and remove Brick as a dependency. Which means that we could just change ItemConfigurable to include the protocol declaration of SpotConfigurable.
Hi, for now we have
View
adoptingSpotConfigurable
, which confuses, at least for me at first. BecauseSpotConfigurable
involves something that can be configurable on theSpotable
object, instead of theView
The text was updated successfully, but these errors were encountered: