Add optional limit and orderBy to dev api chat endpoint #2559
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
timothycarambat
deleted the
2556-feature-workspace-chat-history-dev-api-improvements
branch
|
When can expect the release of this in Docker hub @timothycarambat |
|
@kabaluyot everytime a PR is merged it kicks off a build, when the build from a PR or an future build completes - it is live on This was the PR build https://github.com/Mintplex-Labs/anything-llm/actions/runs/11602168410 So its live now. |
|
Thanks, I was tracking from the Releases |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Pull Request Type
Relevant Issues
resolves #2556
What is in this change?
limitandorderByquery params to the/v1/workspace/:slug/chatsdeveloper endpoint for better control overAdditional Information
Developer Validations
yarn lintfrom the root of the repo & committed changes