This creates lots of queries being sent, (1 dataCube + 3 component types * n component values/minmax).
It's good that these queries exist individually but in my case, I want to fetch more metadata of a cube early and use that to construct the UI.
I wonder if it would be possible/reasonable to have a cube-level method which fetches all of this metadata using less queries than I'm currently doing.
Side note: the dimension values I'm interested here are at the moment all of them, regardless of any filters applied. So maybe it would make sense to just provide them as component extraMetadata? componentValues (which respects filters) is also useful to keep but a slightly different use case.
Follow-up on #32
Currently I'm doing something like this:
This creates lots of queries being sent, (1 dataCube + 3 component types * n component values/minmax).
It's good that these queries exist individually but in my case, I want to fetch more metadata of a cube early and use that to construct the UI.
I wonder if it would be possible/reasonable to have a cube-level method which fetches all of this metadata using less queries than I'm currently doing.
Side note: the dimension values I'm interested here are at the moment all of them, regardless of any filters applied. So maybe it would make sense to just provide them as component
extraMetadata
?componentValues
(which respects filters) is also useful to keep but a slightly different use case.