v0.1.2

Fixed

• The documentation and the package summary no longer claim htmx support
  the page does not have. SpecFormView reads no htmx header, so an htmx
  post is answered as any other: a success is the redirect, which the request
  follows itself, and a refusal is the whole page at its 4xx status, which htmx
  does not swap by default. The PyPI summary called the page htmx-capable and
  listed htmx among its keywords, the README and the documentation site named
  htmx as a client of the JSON views, and the page's documentation and the
  view's docstring named htmx as a client that reads a refused post's status.
  They now say what the page does, and that a fragment answer for htmx is
  planned for 0.2.0. The JSON views are described as serving a script or a
  fetch(), since htmx swaps HTML. Two tests hold the page's answer to an htmx
  post. No behaviour changed.