Introduce EvaluationContext, that is well typed
afsalthaj opened this issue · comments
Currently there is no concept of evaluation context, which can act as a global namespace for expression evaluator, to evaluate selection-field logic which can be arbitrary selection of a field or specific fields from global namespaces such as request, worker metadata , worker-response (which may or may not be a proper result) etc.
As of now, every input is just TypeAnnotatedValue which apparently got broken, after the introduction of refined worker response which can be unit, or multiple results or single result. Also, it has become difficult to maintain as everything got converted into TypeAnnotatedValue, such that these request details, worker details etc lost their type information as we became ignorant whether or not certain field belong to worker, or request.
This, I think, will be the final touch required before milestone 1.0 in terms of supporting all kind of select-fields user can do.
Unfortunately, I had to bring this along with #473
Find the progress here: #475