WAI
Status Update
No update yet.
Comments
vi...@google.com
i'm afraid this is not that trivial with nullable fields in the database.
right now, Room always finds 1 constructor. For this to work, we'll need to find all constructors, check which fields are null in the cursor and call the right constructor.
otherwise, calling the default one might result in Room passing null values into it when they are non-null.
right now, Room always finds 1 constructor. For this to work, we'll need to find all constructors, check which fields are null in the cursor and call the right constructor.
otherwise, calling the default one might result in Room passing null values into it when they are non-null.
vi...@google.com
Ahh, I didn't know room used `@JvmOverloads` constructors. Neat!
lb...@gmail.com
Mentioned in the original issue, but dropping here too.
It seems you can't have nullable val properties. If I have a class with all val properties, it works fine. It complains about multiple constructors, but it doesn't fail at least
It seems you can't have nullable val properties. If I have a class with all val properties, it works fine. It complains about multiple constructors, but it doesn't fail at least
Description
I request to avoid this restriction, and instead offer a new path for apps, which wold be private from all kinds of accessing it, including USB.
Just like the normal private path on "/data/data/...", but on the external storage instead.
This should provide even more security and privacy than the semi-restriction of reaching "Android" folder.
It can also help to have better backward compatibility with all apps that depend on accessing the path, and to maintain the purpose of the "Android" folder, which was always public, and now it's public only via USB.