-
[OPIK-6058] [FE] Add output_json/input_json support to rule editor filter UI (#6460)
frostbyte_neo 发布于
2026-04-28 14:02:31 +00:00 - [OPIK-6058] [FE] Add output_json/input_json support to rule editor via merged Input/Output entries
Merge nested JSON field access into the existing Input and Output dropdown entries
in the rule editor filter UI (v1 and v2). When no key is provided, the filter
behaves as the original whole-field string search. When a key is provided, it
maps to input_json/output_json on save for nested field access via the backend.- [OPIK-6058] [FE] Scope input/output filter config to trace scope only
The filtersConfig rowsMap entries for input/output were applying to all
scopes, causing span filters to show "key (optional)" instead of "value".
Scope them to isTraceScope so span filters remain unaffected.- [OPIK-6058] [FE] Revision: move key-optional logic out of shared isFilterValid
Address PR review: remove domain-specific field name checks from the
shared isFilterValid utility. The key-optional behavior for input/output
dictionary filters is now handled at the call site in AddEditRuleDialog
by coercing the type to string before validation.下载附件