Replace PagingOptions with property assignments #98
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.
This introduces a breaking change: All configuration is now moved
to properties on the PagingViewController class instead of having to
pass in an instance conforming to the PagingOptions protocol.
This reduces the boilerplate of having to create a separate options
struct when you just need to override a single value. It also means
you can change the options after the PagingViewController has been
initialized. Lastly, this change also means we can introduce better
support for customizations through Storyboard in the future.
Before:
After: