TestPager

suspend fun append(): PagingSource.LoadResult<Key, Value>?

Performs a load of LoadType.APPEND on the PagingSource.

Since Paging's first load is always of LoadType.REFRESH, refresh must always be called first before this append is called.

If PagingConfig.maxSize is implemented, append loads that exceed PagingConfig.maxSize will cause pages to be dropped from the front of loaded pages.

Returns the LoadResult from calling PagingSource.load. If the LoadParams.key is null, such as when there is no more data to append, this append will be no-op by returning null.

suspend fun getLastLoadedPage(): PagingSource.LoadResult.Page<Key, Value>?

Returns the most recent LoadResult.Page loaded from the PagingSource. Null if no pages have been returned from PagingSource. For example, if PagingSource has only returned LoadResult.Error or LoadResult.Invalid.

suspend fun getPages(): List<PagingSource.LoadResult.Page<Key, Value>>

Returns the current list of LoadResult.Page loaded so far from the PagingSource.

suspend fun getPagingState(anchorPosition: Int): PagingState<Key, Value>

Returns a PagingState to generate a LoadParams.key by supplying it to PagingSource.getRefreshKey. The key returned from PagingSource.getRefreshKey should be used as the LoadParams.Refresh.key when calling refresh on a new generation of TestPager.

The anchorPosition must be within index of loaded items, which can include placeholders if PagingConfig.enablePlaceholders is true. For example:

• No placeholders: If 40 items have been loaded so far , anchorPosition must be in 0 .. 39.

• With placeholders: If there are a total of 100 loadable items, the anchorPosition must be in 0..99.

The anchorPosition should be the index that the user has hypothetically scrolled to on the UI. Since the PagingState.anchorPosition in Paging can be based on any item or placeholder currently visible on the screen, the actual value of PagingState.anchorPosition may not exactly match the anchorPosition passed to this function even if viewing the same page of data.

Note that when [PagingConfig.enablePlaceholders] = false, the PagingState.anchorPosition returned from this function references the absolute index within all loadable data. For example, with items0 - 99: If items20 - 30 were loaded without placeholders, anchorPosition 0 references item20. But once translated into PagingState.anchorPosition, anchorPosition 0 references item0. The PagingSource is expected to handle this correctly within PagingSource.getRefreshKey when PagingConfig.enablePlaceholders = false.

suspend fun getPagingState(anchorPositionLookup: (item) -> Boolean): PagingState<Key, Value>

Returns a PagingState to generate a LoadParams.key by supplying it to PagingSource.getRefreshKey. The key returned from PagingSource.getRefreshKey should be used as the LoadParams.Refresh.key when calling refresh on a new generation of TestPager.

The anchorPositionLookup lambda should return an item that the user has hypothetically scrolled to on the UI. The item must have already been loaded prior to using this helper. To generate a PagingState anchored to a placeholder, use the overloaded getPagingState function instead. Since the PagingState.anchorPosition in Paging can be based on any item or placeholder currently visible on the screen, the actual value of PagingState.anchorPosition may not exactly match the anchorPosition returned from this function even if viewing the same page of data.

Note that when [PagingConfig.enablePlaceholders] = false, the PagingState.anchorPosition returned from this function references the absolute index within all loadable data. For example, with items0 - 99: If items20 - 30 were loaded without placeholders, anchorPosition 0 references item20. But once translated into PagingState.anchorPosition, anchorPosition 0 references item0. The PagingSource is expected to handle this correctly within PagingSource.getRefreshKey when PagingConfig.enablePlaceholders = false.

suspend fun prepend(): PagingSource.LoadResult<Key, Value>?

Performs a load of LoadType.PREPEND on the PagingSource.

Since Paging's first load is always of LoadType.REFRESH, refresh must always be called first before this prepend is called.

If PagingConfig.maxSize is implemented, prepend loads that exceed PagingConfig.maxSize will cause pages to be dropped from the end of loaded pages.

Returns the LoadResult from calling PagingSource.load. If the LoadParams.key is null, such as when there is no more data to prepend, this prepend will be no-op by returning null.

suspend fun refresh(initialKey: Key? = null): PagingSource.LoadResult<Key, Value>

Performs a load of LoadType.REFRESH on the PagingSource.

If initialKey != null, refresh will start loading from the supplied key.

Since Paging's first load is always of LoadType.REFRESH, this method must be the very first load operation to be called on the TestPager before either append or prepend can be called. However, other non-loading operations can still be invoked. For example, you can call getLastLoadedPage before any load operations.

Returns the LoadResult upon refresh on the PagingSource.