enablePlaceholder | lightweight jQuery plugin to enable same HTML5 | Frontend Framework library

You're running an older version of Retrofit without coroutine support.

To enable support for suspend functions, upgrade Retrofit to version 2.6.0 or higher.

The immediate issue I see is that you are using collect instead of collectLatest. Since submitData does not return, you will never receive updates from your Flow.

You can simplify combining using combineTuple (which is available as a library that I wrote for this specific purpose) (optional)

Afterwards, you can use the liveData { coroutine builder to move execution to background thread

Now your code will look like

Assuming you still have one recyclerview, you can do something like:

I do not believe you can sort correctly on the receiving end when you are using a paging source. This is because paging will return a chunk of data from the database in whichever order it is, or in whichever order you specify in its query directly.

Say you have a list of names in the database and you want to display them sorted alphabetically.

Unless you actually specify that sorting in the query itself, the default query will fetch the X first names (X being the paging size you have configured) it finds in whichever order the database is using for the results of that query.

You can sort the results alright, but it will only sort those X first names it returned. That means if you had any names that started with A and they happened to not come in that chunk of names, they will only show when you have scrolled far enough for them to be loaded by the pager, and only then they will show sorted correctly in the present list. You might see names moving around as a result of this whenever a new page is loaded into your list.

That's for sorting, now for search.

What I ended up doing for my search was to just throw away the database's own capability for searching. You can use " LIKE " in queries directly, but unless your search structure is very basic it will be useless. There is also Fts4 available: https://developer.android.com/reference/androidx/room/Fts4

But it is such a PIA to setup and make use of that I ended up seeing absolutely no reward worth the effort for my case.

So I just do the search however I want on the receiving end instead using a Transformations.switchMap to trigger a new data fetch from the database whenever the user input changes coupled with the filtering on the data I receive.

You already have part of this implemented, just take out the contents of the Transformations.switchMap(filters) and simply return the data, then you conduct the search on the results returned in the observer that is attached to the searchAndFilterPokemonPager call.

Filter is the same logic as search too, but I would suggest to make sure to filter first before searching since typically search is input driven and if you don't add a debouncer it will be triggering a new search for every character the user enters or deletes.

In short:

1. sort in the query directly so the results you receive are already sorted
2. implement a switchMap attached to the filter value to trigger a new data fetch with the new filter value taken into account
3. implement a switchMap just like the filter, but for the search input
4. filter the returned data right before you submit to your list/recyclerview adapter
5. same as above, but for search

I am not sure but I think it was just a bug in the library. I was using 3.0.0-alpha08 but after updating to 3.0.0-alpha09 I don't get any errors. I tested it in my app and in Google sample project after updating the version and it is working.

Fix for IllegalArgumentException being throw when using separators with RemoteMediator and an invalidate is triggered while a remote load that would return endOfPagination is still running (I3a260)

pageSize is just a hint that is sent to LoadParams, paging3 can handle variable page sizes just fine and your PagingSource dorsn't need to respect what loadSize is requested.

Just put whatever number you want to appear in LoadParams.loadSize. Generally it could be something based on the size of your viewport so you can estimate how many days of events to load.

RecyclerView needs a layoutManager, you can set it in the xml:

Okay I've managed to solve this leak. The leak was caused, because I've injected my ShopAdapter via Constructor Injection into my Fragment. When injecting something into the fragment via constructor injection, you have to pass the dependency to the MainFragmentFactory. But because of this, the MainFragmentFactory will always hold a reference to the adapter, even when the fragment is destroyed and the fragment is not needed any more (therefore, requireView().findViewById(R.id.rv_shop).adapter = null wont't even make a change here).

To solve this problem, DON'T inject the Adapter via constructor injection and rather inject it via field injection.