Kevin Ansfield 7c4674507e Switched members-count-fetcher to use members-count-cache ... no issue In the new publish flow we use `{{members-count-fetcher}}` to show member counts as needed in the template without needing to worry about manually fetching counts in the backing classes. However, when switching between states in the flow the count would be re-requested resulting in some glitchy looking async count rendering. By changing `{{members-count-fetcher}}` to use our `members-count-cache` service internally we reduce the likelihood of an async count being triggered when switching between publish flow states. - updated `members-count-cache` service methods to work with filter strings or full query objects - switched `members-count-fetcher` resource to use `members-count-cache` in place of directly querying the store		2022-05-05 11:18:49 +01:00
..
admin	Switched members-count-fetcher to use members-count-cache	2022-05-05 11:18:49 +01:00