Hi there, In fixing the bug regarding count of a list API today, I cannot help wondering why we cannot have separate "Count" api for such purpose rather than bundling this information with list API, where we basically return some information that some users will just throw away since they only care about count for dashboard purpose. I also noticed that in our DB schema, we actually have a table "resource_count" there, not sure the original rational behind this table. If we can take advantage of this table (and keep the information there up-to-date), we may be able to provide a very efficient way to implement such "Count' apis for most commonly used cases. Any thoughts on this?
Thanks -min
