Inaccuracy in the documentation of the Joplin Data API (POST /resources) or a bug in the program

[Marph]

I observed the same issue some time ago:

Feat: can resource api support put function?

At least with Joplin 2.7.13, it was possible to modify the title only. However, there might be different behaviour due to the latest changes: # creating a resource like described in https://joplinapp.org/api/references/rest_api/#post-resources -> success curl -F 'data=@./test/grant_authorization_button.png' -F 'props={"title":"my resource title"}' http://localhost:41184/resources?token=<YOUR_TOKEN> # omitting the props field -> fails with HTTP 500 curl -F 'data=@./test/grant_authorization_butt…

Imo. it would be helpful to align documentation and implementation.