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
The API docs for the edit bookmark action say that you need to provide an id to identify the bookmark being edited, and then provide the modified fields.
After creating a bookmark, if I try to edit it via the API and introduce a tag with the following JSON body
{
"id": 1,
"tags": [
{
"name": "examples"
}
]
}
The server returns a HTTP 500 error with the message: title must not be empty.
After I add the title, I still get an HTTP 500 error but with the message: failed to clean URL: URL is not valid
After both title and url are added to the JSON, API request succeeds
This is in disagreement with the documentation since in this situation neither the title nor url were being modified, and hence should not have been required.
Expected behavior
The API docs either mention that the title and URL fields are always required, or the server is modified to match the documentation.
I've gotten rid of the "Steps to reproduce" heading since it seemed tedious and unnecessary to note down all the steps I did in httpie, but I can do it if it helps, just ask.
The text was updated successfully, but these errors were encountered:
Data
Describe the bug / actual behavior
The API docs for the edit bookmark action say that you need to provide an
id
to identify the bookmark being edited, and then provide the modified fields.After creating a bookmark, if I try to edit it via the API and introduce a tag with the following JSON body
The server returns a HTTP 500 error with the message:
title must not be empty
.After I add the title, I still get an HTTP 500 error but with the message:
failed to clean URL: URL is not valid
After both title and url are added to the JSON, API request succeeds
This is in disagreement with the documentation since in this situation neither the title nor url were being modified, and hence should not have been required.
Expected behavior
The API docs either mention that the title and URL fields are always required, or the server is modified to match the documentation.
Notes
I discovered the problem from integration testing while trying to write an API client for Shiori to use in my Android app
I've gotten rid of the "Steps to reproduce" heading since it seemed tedious and unnecessary to note down all the steps I did in httpie, but I can do it if it helps, just ask.
The text was updated successfully, but these errors were encountered: