Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Partly, this is my fault -- val is not that useful in the @Model context, since @Model relies on mutability. I am used to thinking in terms of immutable viewstates and screwed this up.
However, it probably should not crash this way. Either it should work (with a never-changing value) or it should fail with a "are you *really* sure you want this here?" sort of error.
However, it probably should not crash this way. Either it should work (with a never-changing value) or it should fail with a "are you *really* sure you want this here?" sort of error.
Description
I wrote tests for the behaviour I want us to have, but I don't know how to implement it:
it works if we add keys manually:
for (i in 0..1) {
key(i) {
keys[i] = composer.currentCompoundKeyHash
}
}
but I hope we can do something like this automatically as otherwise it is a huge limitation for the savedInstanceState() usage