Custom endpoints are failing with HTTP 422 status code (no body)

[rossbg]

We have our own custom endpoints following which are working fine with librechat-0.7.8 but are failing with librechat-dev:latest images newer than 3 weeks. Are there any important changes regarding those that can explain this?

[danny-avila]

Yes lots of changes to the underlying HTTP calls being made. Are you using proxies? Any specific custom endpoints I can help you test with?

[rossbg]

Looks like the custom endpoints now work with the complex structure of /chat/completions API

E.g instead of messages with the structure:

{
"role": "user",
"content": "Hello!"
}

they are now sent like this

"content": [
{
"type": "text",
"text": "Hello"
}
]

Can you point me to the specific commit that introduces this and probably other related changes so that we can adapt our custom endpoints?

Many thanks in advance!

[danny-avila]

Ok I see, I can add an option to "force" the legacy content strings, please make an issue requesting this feature specifically to help track this.

[rossbg]

no need actually, we've adapted our backend to handle the new format as this is the way forward