1.6.1

Release 1.6.1

- Fixes a bug in which modifications to the field labeled "Private Key"
  in the UI would instead update the public key.

1.6.0

Release 1.6.0

- Adds support for allowing 'PATCH' request to ignore trailing newlines
  when calculating content insertion position.  Thanks to @cdloh for
  putting this together! (#55)
- Adds support for automatically creating missing directory segments in
  a POST or PUT path.  Thanks @SettingDust for bearing through the PR
  review process! (#44)
- Adds functionality allowing you to bind the API service to a host of
  your choice. This might be useful for users who know what they're
  doing and would like to, for example, run Obsidian in a container like
  obsidian-remote (which I personally use, too -- thanks @sytone for
  making that available!).  (#18)
- Allows you to specify the header in which to look for the
  Authorization tokens.  By default, this is 'Authorization', but
  perhaps you're running Obsidian behind Nginx or some other service,
  and you'd like that tool to look for _its_ authorization tokens in
  the 'Authorization' header.  Now you can tell this plugin to look for
  the token in whatever header you'd like.  Thanks, @derekantrican for
  putting this together as a feature! (#61)
- Significant updates to the plugin settings panel including:
    - Improvements in wording around how we describe the non-encrypted
      HTTP server.
    - Change how we present the buttons used for resetting settings and
      resetting crypogaphy.
    - A new 'Advanced Settings' section in which you can:
        - Directly set your API key (maybe you want all of your Obsidian
          instances to use the same one?)
        - Directly setting your certificate, private key, and public key
          (possibly for the same reason)
        - Configuring the name of the header we'll look in to find your
          authorization token (see above).
        - Configuring the hostname the server binds to.

1.5.2

Release 1.5.2

- Fixes bug preventing downloading of binary files. (Fixes #48)

1.5.1

Release 1.5.1

- Adds /active/ endpoint supporting GET/POST/PUT/PATCH/DELETE-ing
  content of file opened in currently-focused editor pane.

Note: This is a re-release of 1.5.0 that has corrected a couple
packaging and test problems; I clearly was rushing a bit.

1.4.0

Release 1.4.0; Adds Obsidian-Dataview DQL Query Support

- Adds support for Obsidian-Dataview DQL 'TABLE' queries on the /search/
  endpoint.

1.3.9

Release 1.3.9

- Fixes various bugs relating to how directories are handled including
  #21, #22, #23.
- Fixes bug that would cause the server to hang should an unhandled
  exception be raised (#24).

Note that this is a re-release of 1.3.7 (and 1.3.8) because I performed
the release process incorrectly in two different ways.

1.3.5

Release 1.3.5

- #13: Fixes redirect for periodic notes in which folder path contains
  non-ascii characters.

1.3.4

• #13: Fixes bug in handling of non-ascii filenames.
• #15: Fixes bug causing PATCH to a newly-created periodic note to complete unsuccessfully.
• #10: Fixes bug preventing user from updating insecure HTTP port
  (thanks @ericzinnikas!).

1.3.1

Release 1.3.1: Fixes bugs relating to globs & /search/ behavior

- Fixes a bug in which globs having a leading `*` would not match.
- Fixes a bug in which searching using a `{"var": ` pointing at a value
  that might be `null` in some of your files would cause search to fail
  gracelessly.
- Adds name of the file currently under examination to the error message
  emitted when a search exception is raised.

1.3.0

Release 1.3.0: New /open/ route, 'glob' and 'regexp' search operators.

- Adds a new /open/ route allowing you to command Obsidian into
  opening a particular file in the UI.
- Adds new query operators for use with /search/ to expand the
  possibilities of your search including:
  - `glob`: Compares a specified value with a glob so you can, for
    example, match both files having a frontmatter field `usa.oregon`
    and `usa.california` by using a glob like `usa.*`.
  - `regexp`: Compares a specified value with a regular expression
    for exactly the same reasons as are described above, except
    slightly more difficult to use with strings like URLs.
- Adds new `X-Response-Time` header indicating the amount of time
  a particular request took to be rendered.  This is intended for
  debugging purposes, but might be useful for other purposes, too.