Closed msaf1980 closed 4 months ago
Reason for do this - use expr methods in separate product. Use for configure it with carbonapi app config is bad design.
@npazosmendez Another variant of expr refactor. It's compromise (global evaluator exist, but only in expr). May be less clear, but more simple and no Do changes is required.
Not complete solution. https://github.com/go-graphite/carbonapi/pull/818 solved more problems, but required functions Do signature change
There's other cases that are even more tricky, or maybe even impossible. For example aliasQuery
Try to refactor expr package for avoid direct usage zipper/limiter from carbonapi app global config. Not a complete refactor, no separate Eval/Fetch (may be in future).