# compose

Michal Klimczak

12/01/2021, 2:14 PM
I have a feeling that the change that made accompanist Pager based on LazyRow / LazyColumn introduced a lot of issues. And it's a bit difficult to understand what is the team's current stand on this, the issues on github didn't receive any attention lately. Downgrading is painful, as the compatibility with compose (and therefore the kotlin version) usually needs to be pretty strict. I started wondering if I should maybe get the
version and try to make it compatible with new compose. Anyone knows what is the roadmap here?


12/01/2021, 2:19 PM
What issues are you referring to? Some of them are probably working as intended

Michal Klimczak

12/01/2021, 2:21 PM
this one is mine: but I skimmed over issues list and there's lots of recent pager-related ones
"older" pager had the same issue, which you fixed, but switching to LazyRow reintroduced it

Stylianos Gakis

12/01/2021, 2:26 PM
This one as well, we actually downgraded to 0.18.0 because of it.

Andrey Kulikov

12/01/2021, 2:45 PM
I am going to triage those bugs soon. lets discuss each issue individually in the corresponding bugs. but if you think the new implementation absolutely doesn’t work for you you can just copy the implementation from 0.18 into your project. for example I am not yet sure how to implement the page skipping described here
👍🏽 1
🙏 1

Michal Klimczak

12/01/2021, 2:47 PM
yeah, I thought it might be tricky for LazyRow... I can actually wait a week or two, if nothing interesting comes up, will copy, thanks for letting me know :)