If actions are provided by backends, then there may be some actions that are not in BrowserFeatureAction enum. Is that okay?
@Stiivi:
That is ok. Through the list of actions (not sure if the best name name, should be rather methods or even better but more generic capabilities) the backend is telling us how much of the interface it has implemented or is capable of doing. For example, we might have a backend that can provide aggregate data but can't provide data at the fact/record level.
Other potential capabilities that are not actions: split/split_cell, negated_cuts.
From the short discussion here:
@martianboy:
@Stiivi:
Other potential capabilities that are not
actions
:split
/split_cell
,negated_cuts
.