Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 22:23:50 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #2507] [CLOSED] Feature/thread creation slug name #4016

New Issue
Closed
opened 2026-02-22 18:34:58 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:34:58 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/2507
Author: @abrakadobr
Created: 10/20/2024
Status: ❌ Closed

Base: master ← Head: feature/thread-creation-slug-name

📝 Commits (2)

  • c9ccfad thread creation additional params name and slug, with api
  • 49d09c9 typo fix

📊 Changes

2 files changed (+12 additions, -9 deletions)

View changed files

📝 server/endpoints/api/workspaceThread/index.js (+9 -6)
📝 server/models/workspaceThread.js (+3 -3)

📄 Description

Pull Request Type

  • [x ] ✨ feat

What is in this change?

Optional slug and name params for workspace thread creation to use with api.

Additional Information

Without slug param there is no way to identify thread by some 3rd party uuid4 with api. It's possible to store somewhere additional relation of "3rd party uuid4 - threadSlug", but with having ability of defining thread slug manually - this will be not required - thread slug will be equal to "3rd party uuid" so it will be easy to get required thread.

With thread name definition - it will be easy to use UI as "admin tool for viewing results of api based chats "

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • [x ] Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/2507 **Author:** [@abrakadobr](https://github.com/abrakadobr) **Created:** 10/20/2024 **Status:** ❌ Closed **Base:** `master` ← **Head:** `feature/thread-creation-slug-name` --- ### 📝 Commits (2) - [`c9ccfad`](https://github.com/Mintplex-Labs/anything-llm/commit/c9ccfad35e77860a549b2f68ff71787431ebd47e) thread creation additional params name and slug, with api - [`49d09c9`](https://github.com/Mintplex-Labs/anything-llm/commit/49d09c9c2b2e94844345fc18c7940983a7f1e942) typo fix ### 📊 Changes **2 files changed** (+12 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `server/endpoints/api/workspaceThread/index.js` (+9 -6) 📝 `server/models/workspaceThread.js` (+3 -3) </details> ### 📄 Description ### Pull Request Type - [x ] ✨ feat ### What is in this change? Optional slug and name params for workspace thread creation to use with api. ### Additional Information Without slug param there is no way to identify thread by some 3rd party uuid4 with api. It's possible to store somewhere additional relation of "3rd party uuid4 - threadSlug", but with having ability of defining thread slug manually - this will be not required - thread slug will be equal to "3rd party uuid" so it will be easy to get required thread. With thread name definition - it will be easy to use UI as "admin tool for viewing results of api based chats " ### Developer Validations - [x] I ran `yarn lint` from the root of the repo & committed changes - [x ] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:34:58 -05:00
yindo closed this issue 2026-02-22 18:34:58 -05:00
yindo changed title from [PR #2507] Feature/thread creation slug name to [PR #2507] [CLOSED] Feature/thread creation slug name 2026-06-05 15:16:24 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#4016
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?