Hi all,
I was scratching my head for a while wondering how the aggregate implementation was supposed to work until I realised that it probably relies on aggregate checks being subscription based so that check[:issued] is the same for every event.
Does anyone use aggregates with standalone checks? Am I missing something? If not I think it would be useful to state this limitation in the docs.
Cheers,
Rob
It is true, aggregates do not work on standalone checks.
I've tried really hard to get a standalone-version of the
check-aggregates working, but I was unsuccessful.
Yes please, can you PR on the docs repo to make it more clear?
On Thu, Apr 2, 2015 at 3:11 AM, Rob Zissou <roobert@gmail.com> wrote:
Hi all,
I was scratching my head for a while wondering how the aggregate
implementation was supposed to work until I realised that it probably relies
on aggregate checks being subscription based so that check[:issued] is the
same for every event.Does anyone use aggregates with standalone checks? Am I missing something?
If not I think it would be useful to state this limitation in the docs.Cheers,
Rob