Fixed
Status Update
No update yet.
Comments
sk...@gmail.com
that is a bug. we should be able to resolve it properly.
yb...@google.com
interesting, this works fine if the generic field is public final but does not work w/ getters setters.
yb...@google.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.
sk...@gmail.com
should be fixed in 1.1.0-alpha3
Description
Version used: 1.1.0-alpha1
Devices/Android versions reproduced on: Compiled with API 27
This worked with Room 1.0.0, but now fails probably because it doesn't look past the first constructor when searching for one to use.
```
data class MyComplexClass @JvmOverloads constructor(
@field:Relation(parentColumn = "uid", entityColumn = "uid", entity = OtherThing::class)
var otherThings: Set<OtherThing> = setOf(),
@field:Embedded
val mainThing: MainThing)
```
Now it fails the build with `Error:(70, 2) error: Fields annotated with @Relation cannot be constructor parameters. These values are fetched after the object is constructed.` even though there is a valid constructor that only accepts a `MainThing` object and a valid setter that sets the `@Relation` field.