Handling complex/object values in a field #853
-
|
I have a custom ruleProcessor that renders a more complex, nested SQL statements for a field. How would I do that? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
Could you provide some sample code, showing what you have to work with so far and where you need what information? |
Beta Was this translation helpful? Give feedback.
-
|
sure, so I have the following custom ruleProcessor working fine so far: const customRuleProcessor: RuleProcessor = (rule, options) => {
const categoryMinScore = 0.5
if (rule.field === 'category.google.id') {
const values = rule.value.map((val: string) => `'${val}'`).join(',')
return (rule.value as string[]).length > 0
? `(EXISTS (SELECT 1 FROM UNNEST(category.google) AS g WHERE g.id IN (${values}) AND CAST(g.score AS FLOAT64) > ${categoryMinScore}))`
: ''
}
// other fields custom handling
return defaultRuleProcessorSQL(rule, options)
}and now I want to make the another approach could be to customize the "category" multi-select ValueEditor I have even further and render a secondary input. but then I would have to manage a complex value object which might be a bigger hassle. any help appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
I apologize for taking so long to respond! My recommendation would actually be the same as your last suggestion, storing an object in the const query: RuleGroupType = {
combinator: "and",
rules: [
{
field: "category.google.id",
operator: "exists", // or whatever
value: {
categoryMinScore: 0.5,
values: ["one", "two", "etc"]
}
}
]
}You're right that it's a bigger hassle, but usually it's not much more than this: const MyValueEditor = (props: ValueEditorProps) => {
const updateValue = (k: string, v: any) => {
props.handleOnChange({ ...props.value, [k]: v });
};
return (
<>
// use updateValue('categoryMinScore', e.target.valueAsNumber)
// and updateValue('values', <list of values>)
// in here
</>
);
};The "not much more" part would include initialization and validation of |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the confirmation and hint. I got it working. For anyone coming here, this is my implementation: function SelectWithSearch({ handleOnChange, ...otherProps }: ValueEditorProps): React.ReactElement {
const onChangeObjectValue = (k: string, v: string[] | string): void => {
handleOnChange({ ...otherProps.value, [k]: v })
}
if (otherProps.field === 'category.google.id') {
const categories = otherProps.value.categories === undefined ? [] : otherProps.value.categories
const score = otherProps.value.score === undefined ? '0.5' : otherProps.value.score
return (
<>
<Autocomplete
disableCloseOnSelect
options={otherProps.values as Option[]}
value={(categories as string[]).map((val) =>
(otherProps.values as Option[]).find((option) => option.name === val)
)}
getOptionKey={(option: Option) => option.name}
multiple
onChange={(_event, value) => {
onChangeObjectValue(
'categories',
value.map((option: Option) => option.name)
)
}}
sx={{ width: 'stretch' }}
renderInput={(params) => <TextField {...params} variant='standard' placeholder='Select categories' />}
/>
<TextField
variant='standard'
type='number'
value={score}
onChange={(e) => {
onChangeObjectValue('score', e.target.value)
}}
sx={{ input: { textAlign: 'center' }, width: '65px', alignSelf: 'end' }}
slotProps={{
htmlInput: { min: '0', step: '0.1', 'data-testid': 'categoryScore' }
}}
/>
</>
)
}
return <MaterialValueEditor handleOnChange={handleOnChange} {...otherProps} />
} |
Beta Was this translation helpful? Give feedback.
I apologize for taking so long to respond! My recommendation would actually be the same as your last suggestion, storing an object in the
valuefield. A query would end up looking something like this, I presume:You're right that it's a bigger hassle, but usually it's not much more than this: