Filterx unmarshal does not cause variables to be dirty#446

Merged

OverOrion merged 7 commits intoaxoflow:mainfrom bazsi:filterx-unmarshal-does-not-cause-variables-to-be-dirty

Jan 22, 2025

+159-118

Commits on Jan 18, 2025

filterx/filterx-scope: add filterx_variable_handle_is_message_tied() in addition to is_floating
bazsi
committed
filterx/filterx-eval: remove partial support for multiple LogMessage instances
bazsi
committed
filterx/expr-variable: make template macro based variables read only
bazsi
committed
filterx/filterx-variable: move FilterXVariableHandle related functions to the front
bazsi
committed
filterx/filterx-variable: rename filterx_variable_free to _clear()
bazsi
committed
filterx/filterx-variable: introduce "variable_type" at the variable layer
bazsi
committed
filterx: do not consider unmarshaling a change in value
bazsi
committed