murtaza-nasir/speakr v0.8.18-alpha

v0.8.18-alpha — API v1 folder operations

on GitHub

v0.8.18-alpha — API v1 folder operations

Patch release on top of v0.8.17-alpha. Follow-up to #274.

The folder resource endpoints (CRUD on /api/v1/folders) shipped in v0.8.16-alpha, but recordings had no way to be moved into or out of those folders via the v1 API. This release closes that gap so companion apps can actually use folders for recording management.

Added

• GET /api/v1/recordings?folder_id=<id> filters the list response to recordings in the given folder. Pass ?folder_id=none to list recordings that are not in any folder.
• PATCH /api/v1/recordings/{id} accepts folder_id in the JSON body to move an existing recording into a folder. Pass null to remove the recording from its folder. Permission model matches the rest of the v1 API: personal folders require ownership, group folders require membership.
• PATCH /api/v1/recordings/batch accepts folder_id inside updates to bulk-move all listed recordings into the same destination. The target folder is validated once up front rather than per recording.

OpenAPI

The schema at /api/v1/openapi.json reflects all three additions, so Swagger UI and generated clients pick them up automatically. The batch PATCH spec also gained explicit documentation for is_inbox, is_highlighted, add_tag_ids, and remove_tag_ids, which were already supported but undocumented.

No breaking changes

Existing endpoints continue to behave identically when folder_id is omitted from the request.