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
- remove hidden supplementary view hacks, close#47
- fix `SupplementaryViewKind` models, close#56
- `RegistrationMethod` --> `ViewRegistrationMethod` (and remove nesting, since this will apply to all cells in #18)
- make `kind` a property of `SupplementaryViewInfo`
- Remove `typealias Section`, only used in one place and doesn't add any value
This still needs all kinds of work to correctly model how collection view supplementary views work, but this is a start.
We're artificially (and implicitly) restricted to headers and footers. We'll probably have to keep this limitation for 1.0.
This aims to make a more general transition easier.
- Make `kind` a property of `SupplementaryViewInfo`
- Make `ViewRegistrationMethod` a proper type on its own (which we can use for cell registration in #18)
Our model here is incorrect.
public enum SupplementaryViewKind
is simply wrong.kind
should be a property onSupplementaryViewInfo
Like I mentioned in #55, supplementary views can be arbitrary. So can
kind
.For example, you can use the same cell prototype and reuseIdentifier, but different
kind
specifiers. We currently can't support this.Practical use case: a cell with a label could be used as a header and footer.
The text was updated successfully, but these errors were encountered: