Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
So in Compose everything is like state machine and it is always in some state.
Are you saying that loadState being null is more correct initial state compared to the current
```
CombinedLoadStates(
refresh = InitialLoadStates.refresh,
prepend = InitialLoadStates.prepend,
append = InitialLoadStates.append,
source = InitialLoadStates
)
private val IncompleteLoadState = LoadState.NotLoading(false)
private val InitialLoadStates = LoadStates(
IncompleteLoadState,
IncompleteLoadState,
IncompleteLoadState
)
```
Are you saying that loadState being null is more correct initial state compared to the current
```
CombinedLoadStates(
refresh = InitialLoadStates.refresh,
prepend = InitialLoadStates.prepend,
append = InitialLoadStates.append,
source = InitialLoadStates
)
private val IncompleteLoadState = LoadState.NotLoading(false)
private val InitialLoadStates = LoadStates(
IncompleteLoadState,
IncompleteLoadState,
IncompleteLoadState
)
```
Description
LazyPagingItems
in paging-compose:1.0.0-alpha16 added an init block to implement paging.Logger interface from paging-common:3.2.0-alpha02.To ensure compatibility between the two artifacts, paging-compose:1.0.0-alpha16 should have a constrained dependency on paging-common:3.2.0-alpha02 or higher.