🐛 fix: Assistants Endpoint Handling in createPayload
Function
#8123
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Closes #8100
I fixed the logic in the createPayload function to properly build the server URL for Assistants endpoints, ensuring endpointType is respected and that '/modify' is appended only for edited payloads. I also bumped the librechat-data-provider package version to 0.7.89 to reflect the update.
Change Type
Testing
I manually tested assistant endpoint payloads with and without edits, verifying that the URLs are constructed accurately for both 'assistants' and 'azureAssistants'. I recommend running regression tests for conversations using these endpoints, and checking that modified payloads reach the /modify route only when editing is intended.
Test Configuration:
Checklist