Before, when the user would configure the chatModel, we would send a request to the backend. If the backend successfully configured the model, then the frontend would send a further request to add the info message to the chat history, eg 'changed frequencyPenalty to 0.6'.
This PR changes it so that when the backend successfully configures the chatModel, the backend generates the info message and appends it to the history, then forwards it on to the frontend.
Notes
handleConfigureModel now generates an info message, appends it to the chat history and forwards it to the frontend.
renames MODEL_CONFIG enum to MODEL_CONFIG_ID and converts it to a string literal type, on frontend and backend.
Description
Before, when the user would configure the chatModel, we would send a request to the backend. If the backend successfully configured the model, then the frontend would send a further request to add the info message to the chat history, eg 'changed frequencyPenalty to 0.6'.
This PR changes it so that when the backend successfully configures the chatModel, the backend generates the info message and appends it to the history, then forwards it on to the frontend.
Notes
handleConfigureModelnow generates an info message, appends it to the chat history and forwards it to the frontend.MODEL_CONFIGenum toMODEL_CONFIG_IDand converts it to a string literal type, on frontend and backend.handleConfigureModel.handleConfigureModel.Checklist
Have you done the following?