Fix conversation history handling when history_turns is 0
• Check history_turns > 0 before filtering • Prevent sending all history converstion to backend when history_turns is 0
This commit is contained in:
parent
6e2eab5c23
commit
62aa0726a5
1 changed files with 6 additions and 4 deletions
|
|
@ -261,10 +261,12 @@ export default function RetrievalTesting() {
|
||||||
const queryParams = {
|
const queryParams = {
|
||||||
...state.querySettings,
|
...state.querySettings,
|
||||||
query: actualQuery,
|
query: actualQuery,
|
||||||
conversation_history: prevMessages
|
conversation_history: (state.querySettings.history_turns || 0) > 0
|
||||||
.filter((m) => m.isError !== true)
|
? prevMessages
|
||||||
.slice(-(state.querySettings.history_turns || 0) * 2)
|
.filter((m) => m.isError !== true)
|
||||||
.map((m) => ({ role: m.role, content: m.content })),
|
.slice(-(state.querySettings.history_turns || 0) * 2)
|
||||||
|
.map((m) => ({ role: m.role, content: m.content }))
|
||||||
|
: [],
|
||||||
...(modeOverride ? { mode: modeOverride } : {})
|
...(modeOverride ? { mode: modeOverride } : {})
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue