You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a following question (#1894). But I think it would be better to separately report.
After adding a new document with document/raw-text API, I want to remove this document with /system/remove-documents. There is some trouble to remove this document with names property in the DELETE request.
If id is used (i.e. 99502983-20fa-4cd1-bef5-e17cd0c56dae, I get an success response, but the document is still in the workspace.
Then I test the name retrieved from document api, i.e. raw-title-99502983-20fa-4cd1-bef5-e17cd0c56dae.json or ``
Are there known steps to reproduce?
No response
The text was updated successfully, but these errors were encountered:
However, the correct path to put in is the folder + filename - the 200 will return even if the document is not found or deleted to prevent people trying to traverse or remove all documents.
In this case the document should be something like custom-documents/raw-title-99502983-20fa-4cd1-bef5-e17cd0c56dae - however this kind of nature for deletion should be revisited to be more trivial since it is indeed quite unclear.
timothycarambat
changed the title
[BUG]: API remove documents /v1/system/remove-documents
[FEAT]: Improve API remove documents /v1/system/remove-documents
Jul 22, 2024
How are you running AnythingLLM?
AnythingLLM desktop app
What happened?
This is a following question (#1894). But I think it would be better to separately report.
After adding a new document with
document/raw-text
API, I want to remove this document with/system/remove-documents
. There is some trouble to remove this document withnames
property in the DELETE request.If id is used (i.e.
99502983-20fa-4cd1-bef5-e17cd0c56dae
, I get ansuccess
response, but the document is still in the workspace.Then I test the name retrieved from
document
api, i.e.raw-title-99502983-20fa-4cd1-bef5-e17cd0c56dae.json
or ``Are there known steps to reproduce?
No response
The text was updated successfully, but these errors were encountered: