Releases: coddingtonbear/obsidian-local-rest-api
Releases · coddingtonbear/obsidian-local-rest-api
3.2.0
Release 3.2.0 - Adds new /openapi.yaml endpoint via which the current API's OpenAPI Yaml document can be retrieved. This will allow API consumers to inspect the available API endpoints at runtime. Thanks @spammenotinoz for submitting the patch (see also https://github.com/coddingtonbear/obsidian-local-rest-api/pull/151).
3.1.0
Release 3.1.0 - Adds new API endpoints allowing you to interact with periodic notes for arbitrary dates instead of only the current periodic note.
3.0.6
Release 3.0.6 Note: this is a re-release of 3.0.5 and differs from that version only in that this uses a newer version of `jest` to fix a build-related problem. This release fixes a handful of problems various folks encountered while using the new (V2) PATCH functionality. - #140, #139 - When a patch failed to be applied, instead of returning an error message, the server would hang. Thanks @7shi for the fix! - #142 - If you supplied JSON content that encoded anything other than an object, your incoming content would not be parsed and your patch would fail. Now, we use the non-strict JSON parsing mode that allows you to provide any arbitrary JSON content.
3.0.5
Release 3.0.5 This release fixes a handful of problems various folks encountered while using the new (V2) PATCH functionality. - #140, #139 - When a patch failed to be applied, instead of returning an error message, the server would hang. Thanks @7shi for the fix! - #142 - If you supplied JSON content that encoded anything other than an object, your incoming content would not be parsed and your patch would fail. Now, we use the non-strict JSON parsing mode that allows you to provide any arbitrary JSON content.
3.0.4
Release 3.0.4 - Additional necessary fixes for the bug described in #138. The fixes packaged in 3.0.3 addressed only /vault/ GET and /open/ POST, but there are a few other HTTP methods, too, that needed the fix for the /vault/ route.
3.0.3
Release 3.0.3 - Fixes a bug that would prevent users from using /vault/* or /open/* routes with paths having spaces or non-ascii characters. (#138).
3.0.2
Release 3.0.2 - Adds deprecation warning in HTTP response and logs when using deprecated (2.0) PATCH API.
3.0.1
Release 3.0.1 - Adds new PATCH implementation that allows one to alter markdown documents relative to not only a specified heading, but also frontmatter fields and block references, too. This older (now undocumented) PATCH mechanism will continue to work, but is now deprecated and will be removed in 4.0. - Fixes various bugs and tests.
2.5.4
Release 2.5.4 - Adds new Extension API allowing folks to define their own routes and API functionality via separate Obsidian Plugins. - Want to expose REST API routes as part of your existing plugin? Now you can! - Need an API feature that doesn't quite fit the scope of what Obsidian Local REST API intends to provide? Now you can add your own routes in your own plugin, but let them be served by Obsidian Local REST API.
2.4.3
Release 2.4.3 - Fixes (speculatively) a bug which might prevent any search operations from succeeding if a `null` tag was found on any note. - Minor clean-up and word changes in the configuration panel UI including: - Automatically re-fresh the server status when toggling the HTTP or HTTPs servers on or off. - Include certificate installation notice & instructions in the table showing the HTTPs server status. - Show all subjectAltName options in server status table. - Include 'copy' link for API key.