See https://camlistore-review.googlesource.com/#/c/3688/1 for context.
We eventually want to change describe so that it doesn't return every single
attribute of a permanode, because doing so can be very inefficient (see bug
435).
However, once that it done, it would be nice if describe could allow clients to
get the number of a particular attribute, attribute pattern, or at least
specifically whether there are any 'children' (camliMember or camliPath:*)
attributes for a permanode.
The UI would like to know when laying out a search result whether a permanode
has any children so that it can quickly switch to the correct detail aspect(s)
on click. Without this, we either see stutter in the UI when switching, or have
to block layout of the detail view on a search query.
Original issue reported on code.google.com by zbo...@gmail.com on 3 Sep 2014 at 7:38
Original issue reported on code.google.com by
zbo...@gmail.com
on 3 Sep 2014 at 7:38