Fixed
Status Update
No update yet.
Comments
yb...@google.com
The RecyclerView is a brand new widget in the support library.
There are some known issues with using RecyclerView in the layout rendering and layout editor.
We are working on a fix; you can star this issue if you want to keep track of the progress.
There are some known issues with using RecyclerView in the layout rendering and layout editor.
We are working on a fix; you can star this issue if you want to keep track of the progress.
mm...@commonsware.com
Is there a ETA when this bug is fixed?
I would say it is quiet simple to fix. You just need to use any LayoutManager.
Are there any plans when this View will be published for older platforms? AFIK it works even on Gingerbread.
I would say it is quiet simple to fix. You just need to use any LayoutManager.
Are there any plans when this View will be published for older platforms? AFIK it works even on Gingerbread.
de...@gtempaccount.com
Getting the same error:
"The new RecyclerView does not yet work in Studio. We are working on a fix. (Open
"The new RecyclerView does not yet work in Studio. We are working on a fix. (Open
sk...@gmail.com
Is it going to be best practice to use Recylerview, and Listview essentially deprecate?
be...@google.com
Haven't heard anything for a month. Any progress??
yb...@google.com
ap...@google.com
Any news?
Description
Version used: 1.0.0-alpha3
Devices/Android versions reproduced on: n/a
@Relation must return a List<> or Set<>. This includes cases where we know that there should only be one value (e.g., the parent on a 1:N relation). As it stands, we then need to get the 0th entry out of the List or something to get to our one-and-only entity.
IMHO, @Relation should support return types of a single entity instance. If the query returns 2+ rows, I can see three possible responses:
- Throw an exception
- Return the first row's entity
- Either, configurable via an annotation property (and ideally configurable based on build type, as we might throw the exception on debug builds but stagger along with boffo results in production)
After all, in principle, we should have the exact same code ourselves to deal with the current collection-based response.
I'm uncertain how popular @Relation will turn out to be, so I certainly can't characterize this as especially important. I'm just putting it out there for tracking purposes.
Thanks!