I have a feeling that the change that made accompa...

# compose

[Michal Klimczak]

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 0.18.x version and try to make it compatible with new compose. Anyone knows what is the roadmap here?

[cb]

What issues are you referring to? Some of them are probably working as intended

[Michal Klimczak]

this one is mine: https://github.com/google/accompanist/issues/876 but I skimmed over issues list and there's lots of recent pager-related ones

[Michal Klimczak]

"older" pager had the same issue, which you fixed, but switching to LazyRow reintroduced it

[Stylianos Gakis]

This one as well, we actually downgraded to 0.18.0 because of it.

[Andrey Kulikov]

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 https://github.com/google/accompanist/issues/876

[Michal Klimczak]

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 :)