Handle unknown values when adding power search to unconfigured columns
Reviewed By: antonk52 Differential Revision: D49822513 fbshipit-source-id: a9c5c6ddc91ac6e7284af045ec673144d9c64906
This commit is contained in:
committed by
Facebook GitHub Bot
parent
4165a1b272
commit
76918ae4fe
@@ -256,13 +256,13 @@ export function DataTable<T extends object>(
|
||||
res[operatorConfig.key] = operatorConfig;
|
||||
return res;
|
||||
}, {} as Record<string, OperatorConfig>) ?? {
|
||||
string_contains: dataTablePowerSearchOperators.string_contains(),
|
||||
string_contains: dataTablePowerSearchOperators.string_contains(true),
|
||||
string_not_contains:
|
||||
dataTablePowerSearchOperators.string_not_contains(),
|
||||
dataTablePowerSearchOperators.string_not_contains(true),
|
||||
string_matches_exactly:
|
||||
dataTablePowerSearchOperators.string_matches_exactly(),
|
||||
dataTablePowerSearchOperators.string_matches_exactly(true),
|
||||
string_not_matches_exactly:
|
||||
dataTablePowerSearchOperators.string_not_matches_exactly(),
|
||||
dataTablePowerSearchOperators.string_not_matches_exactly(true),
|
||||
},
|
||||
};
|
||||
res.fields[column.key] = columnFieldConfig;
|
||||
|
||||
Reference in New Issue
Block a user