Fix jinja2 variable naming inconsistencies (#22578)
This commit is contained in:
parent
2423f97c72
commit
7a69b57823
3 changed files with 11 additions and 11 deletions
|
|
@ -309,7 +309,7 @@ const useConfig = (id: string, payload: LLMNodeType) => {
|
|||
return [VarType.number, VarType.string, VarType.secret, VarType.arrayString, VarType.arrayNumber, VarType.file, VarType.arrayFile].includes(varPayload.type)
|
||||
}, [])
|
||||
|
||||
const filterJinjia2InputVar = useCallback((varPayload: Var) => {
|
||||
const filterJinja2InputVar = useCallback((varPayload: Var) => {
|
||||
return [VarType.number, VarType.string, VarType.secret, VarType.arrayString, VarType.arrayNumber].includes(varPayload.type)
|
||||
}, [])
|
||||
|
||||
|
|
@ -356,7 +356,7 @@ const useConfig = (id: string, payload: LLMNodeType) => {
|
|||
structuredOutputCollapsed,
|
||||
setStructuredOutputCollapsed,
|
||||
handleStructureOutputEnableChange,
|
||||
filterJinjia2InputVar,
|
||||
filterJinja2InputVar,
|
||||
}
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue