IssueTracker

You may create a LazyPagingItems through the extension Flow<PagingData>.collectAsLazyPagingItems()

To construct a Flow<PagingData> from static sample data for your preview, you can use PagingData.from(list)

The preview did compile, but no items displayed, other UI components such as Button works fine though.

The code now:

@Preview
@Composable
fun Preview() {
    val usersFlow = flowOf(
        PagingData.from(
            listOf(
                User("123", "33423", "2211", "Makanan", "Dapur", "Risal", "User", "Masakka")
            )
        )
    )

    DefaultTheme {
        Surface() {
            MainUi(
                users = usersFlow.collectAsLazyPagingItems(),
                onEditItem = {},
                onDeleteItem = {}
            ) {

            }
        }
    }
}

I don't know if this is related but the IDE give me this message

High number of internal exceptions has been detected. This indicates a serious problem with the IDE. Please consider clean reinstall of Android Studio. If the problem persists, please report a bug by following the link below.

Build: AI-203.7717.56.2031.7583922, 202107261959,

AI-203.7717.56.2031.7583922, JRE 11.0.10+0-b96-7249189x64 JetBrains s.r.o., OS Linux(amd64) v5.11.0-7620-generic, screens 1920.0x1080.0, 1920.0x1080.0

AS: Arctic Fox | 2020.3.1; Kotlin plugin: 203-1.5.21-release-328-AS7717.8; Android Gradle Plugin: 7.0.0; Gradle: 7.0.2; Gradle JDK: version 11.0.10; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)

Nope, still the same.

In my project preview also doesn't works. I tried all suggestion above.

With compose 1.2.0-beta01, constructing a static LazyPagingItems like this works for me in interactive preview.

val ordersFlow = flowOf(PagingData.from(orders))
val pagingItems = ordersFlow.collectAsLazyPagingItems()

However, the static preview will only show an empty list of items.

Preview doesn't work in paging-compose at the moment with PagingData because it has to wait for some work to be done before any items show up, so the first frame is always empty as mentioned in #5. However, it's worth investigating if we can get it to work with static PagingData like PagingData.from

+1 our snapshot tests became useless after moving from unpaged lists to paged lists, would be really nice to have a preview functionality so our snapshot tests can keep working

Please reopen.

Would be great to reopen this or give a reason why it won't be fixed. Seems like an important functionality since like it currently stands we cannot cover paged lists with paparazzi snapshot tests.

Reopening as it's something we would want for paging-compose.

Paging currently can't support this because as comment #18 mentioned, there needs to be some work done (i.e. collection) before PagingData returns data. This will require some new API which we will look into.

We are planning to include preview support as part of stable paging-compose.

Any dates/timelines?

Currently planned for Q2/Q3.

Fixed internally and will be available in the next Paging release. This bug will be updated with release version at the time.

Is it already in 1.0.0-alpha19? If yes, then could I get an example of how to use it?

It will be available in the upcoming release on May 24th as paging-compose 1.0.0-alpha20.

The change does include an example on how to set up preview for paging-compose

The example has DisplayPaging() composable inlined within PagingPreview() composable. This is ONLY FOR sample purposes because of how the @Preview annotation is rendered in documents. In production code DisplayPaging() should be its own separate, top-level declaration.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.paging:paging-common:3.2.0-alpha06
• androidx.paging:paging-compose:1.0.0-alpha20

One important point – inside @Preview, you should use MutableStateFlow() rather than builders like flowOf() – the latter simply doesn’t work