@protocol HUBContentOperationWithPaginatedContent <HUBContentOperation>
Extended content operation protocol that adds the ability to append paginated content to a view
Use this protocol in case you want to handle large datasets in your feature, which are not practical to load up front. Content operations conforming to this protocol will be called and asked to append content to an existing view model builder in either of 3 scenarios:
- If the
loadNextPageForCurrentViewModelmethod was called on a
- If the user is about to reach the bottom of the view’s content when scrolling.
Append content for a certain page index to an existing view model builder
- (void)appendContentForPageIndex:(NSUInteger)pageIndex toViewModelBuilder: (nonnull id<HUBViewModelBuilder>)viewModelBuilder viewURI:(nonnull NSURL *)viewURI featureInfo:(nonnull id<HUBFeatureInfo>)featureInfo connectivityState:(HUBConnectivityState)connectivityState previousError:(nullable NSError *)previousError;
The index of the page to add content for. Since the main content set is considered index number 0, this will always be at least 1 or greater. Incremented on each paginated content loading chain.
The builder to use to append content to the view. If this content operation is first in the appended content loading chain, this builder will be a snapshot of the last rendered view state. If it’s subsequent in the chain, it will instead be a snapshot of the previous operation’s finished state.
The URI of the view that content should be appended for
Info about the feature that the operation is being performed for
The current connectivity state of the application (as it was when the content loading chain that this operation is part of was started).
Any previous error that was encountered during the content loading chain that this operation is a part of.