Fixed
Status Update
Comments
sh...@google.com <sh...@google.com> #3
yb...@google.com <yb...@google.com> #4
Run
yb...@google.com <yb...@google.com> #5
Run
st...@gmail.com <st...@gmail.com> #7
Adarsh,
Could you please try to determine around what version of RecyclerView this bug seems to have been created? I would first try to reproduce the bug via the version in the sample and then see if it is reproducible betwee RecyclerView 26 all the way up to the AndroidX RecyclerView 1.1.0-alpha04.
Thanks
Could you please try to determine around what version of RecyclerView this bug seems to have been created? I would first try to reproduce the bug via the version in the sample and then see if it is reproducible betwee RecyclerView 26 all the way up to the AndroidX RecyclerView 1.1.0-alpha04.
Thanks
Description
androidx.recyclerview:recyclerview:1.2.0-alpha03
First of all, thank you for the new
MergeAdapter
! This is my first time using and benefiting from it.When I create a merge adapter configuration via
MergeAdapter.Config.Builder().build()
, I receive a configuration withConfig::isolateViewTypes
set tofalse
. The value of this same field inMergeAdapter.Config::DEFAULT
istrue
.This violated the principle of least surprise for me. I was evolving code that initially used "no" (= the default) configuration:
I wanted to update this code to change the stable ID mode. I tried to achieve that by building and passing in a custom configuration:
but this temporarily broke my code because view type isolation changed compared to the initial code. I instead needed to explicitly write
to retain default view type isolation behavior.
Please evaluate whether it would be less surprising to initialize
in
MergeAdapter.Config::Builder
instead!