add support for taking filters as an input about hermes

[trentwatt]

This is something I could possibly take on.

Any thoughts @hkang1 on how to approach?

[trentwatt]

What is the desired API?

setFilters(Hermes.Filter[]).

addFilters(Hermes.Filter[]).

resetFilters()

Do merge and update like from user interactions?

Do we want to apply regardless of whether it's below the threshold required for user-interaction-supplied filters? Or does that cause problems, and we should require threshold?

[hkang1]

What is the desired API?

setFilters(Hermes.Filter[]).

addFilters(Hermes.Filter[]).

resetFilters()

Yeah those three actions sound reasonable. Maybe Hermes.Filters as an input instead so we also know which dimension to apply the filters.

One additional way to add might be to take Filters during Hermes initialization, which would be useful if the dev wanted to build a chart with filters pre applied in one go.

Do merge and update like from user interactions?

Yeah. There is an update routine that "cleans up" filters. Specifically it removes 0-sized filters and also merges overlapping filters within the same dimension. But mimicking user interactions makes sense to me.

Do we want to apply regardless of whether it's below the threshold required for user-interaction-supplied filters? Or does that cause problems, and we should require threshold?

Good question... my initial reaction is that it's probably best to mimick the user interactions, which translates to following the threshold rules.

[hkang1]

removeFilters() could be a useful one too, but referencing the exact filter to remove could be a bit tricky. Would need the dimension key and the index of the filter. e.g. removeFilter('accuracy', 1) would remove the 2nd filter from the accuracy dimension.

[hkang1]

Resolved partially with PR 114.
The config can take initial filters, but no dynamic functions to modify filters on the fly. Will hold off until there are actual use cases to add that capability.