Fixed
Status Update
No update yet.
Comments
mm...@commonsware.com
that is a bug. we should be able to resolve it properly.
yb...@google.com
yb...@google.com
ya...@google.com
interesting, this works fine if the generic field is public final but does not work w/ getters setters.
bo...@gmail.com
ok, turns out we are not properly processing methods when processing pojos.
That is why it works when I use a field.
I've created a CL that fixes the problem. Until it is shipped, you can workaround the problem by making that field public (preferably public final if possible).
Thanks for the report.
That is why it works when I use a field.
I've created a CL that fixes the problem. Until it is shipped, you can workaround the problem by making that field public (preferably public final if possible).
Thanks for the report.
ya...@google.com
should be fixed in 1.1.0-alpha3
ma...@liulishuo.com
Thanks!!!
Description
Version used: 1.0.0-alpha1
Devices/Android versions reproduced on: Android Studio 3.0 Canary 1
There doesn't appear to be a way to add general SQLite column constraints [1] to the generated schema. In particular, my application uses NOT NULL and COLLATE NOCASE on some columns and I would like to be able to have Room generate entities with those clauses.
From what I can see there isn't any "escape hatch" to manually adjust the generated schema to workaround this issue.
1: