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
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
In its current state the provider communicate tableview delegate methods trough ProviderDelegate protocol. The suggestion would be to change this protocol to use closures instead, having a more swift oriented approach.
What are your thoughts on it?
The text was updated successfully, but these errors were encountered:
I don't think the cells should have these closures. I'd see it as something in the provider. The provider hold the closure reference, its owner set them, and finally the provider DelegateHandler call them as needed.
For me makes sense having didSelect and didDeselect as the base ones, since it's what it's mostly used. Other than that, if someone needs to add extra behaviour, the provider can be subclassed and added as necessary.
In its current state the provider communicate tableview delegate methods trough ProviderDelegate protocol. The suggestion would be to change this protocol to use closures instead, having a more swift oriented approach.
What are your thoughts on it?
The text was updated successfully, but these errors were encountered: