Releases: coddingtonbear/obsidian-local-rest-api
Releases · coddingtonbear/obsidian-local-rest-api
3.0.4
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.
2.4.1
Release 2.4.1 Note: This is a re-release of 2.4.0, with an updated package-lock.json. - Updating settings panel to: - Provide direct access to the API connection URL. - Rephrasing things and giving better insight into where folks can find docs and what requests look like.
2.3.0
Release 2.3.0 - Adds toggle allowing user to enable/disable HTTPs server (under 'Advanced Settings'). This toggle is not likely to be useful in cases outside of troubleshooting connection-related problems.
2.2.2
Release 2.2.2 - Fixes a bug in which we'd show that you needed to regenerate your certificate...only when you didn't. And, vice-versa, of course, as things always go.
2.2.1
Release 2.2.1 - Various improvements to how certificate problems are communicated - Adds new warning boxes on the plugin options page when your certificate is invalid or nearing expiry. - Also adds new warning boxes on the plugin options page when your certificate isn't generated with the latest standards that Obsidian Local REST API uses. - Includes information about upcoming certificate expiries and standard compliance in `/` route output when incoming connection is authenticated, too, so other tools like Obsidian Web might be able to warn you when your certificate is nearing expiry. - Moves some settings that really should be considered "Advanced" into "Advanced Settings" including both port settings. - Some minor copy changes for clarity. This is a re-release of 2.2.0.