* fix: change css midBlue saturation and body tag color to a darker color
* feat: add empty alt attribute to decorative bars
* feat: add alt attributes for index link images
* fix: tweak code background alpha
* feat: add custom highlighting theme, change comment color to be legible
* fix: replace a tags with span
* fix: lighten background color of div
* feat: add doctype and meta description
* fix: remove doctype to prevent no quirks mode (why.png)
* Fix hx-on anchor in the docs
* add hx-on to table of contents in the docs
* preserve links integrity
There are most likely links to #the-hx-on-attribute in the wild.
I managed to find one on the Discord at list. Probably best to keep both options
* prevent binary data loss by restructuring forms.
* Update www/content/docs.md
Co-authored-by: Denis Palashevskii <20725046+Renerick@users.noreply.github.com>
* moved the example to example directory
* Updated documentation based on feedback
---------
Co-authored-by: gbourant <root@gbourant.com>
Co-authored-by: Denis Palashevskii <20725046+Renerick@users.noreply.github.com>
* Allow extensions to set request bodies for GET and DELETE
Even though the semantics of request bodies for GET and DELETE are
undefined, it is legal to set request bodies for them. By default, GET
and DELETE form parameters should be encoded as URLs. If, however, an
extension defines `encodeParameters`, that should override the default
and set the request bodies for GET and DELETE methods, just like it does
for all the other HTTP methods.
* Don't use URL params by default with DELETE
* Re-enable skipped DELETE test
* Remove reference to DELETE in comment
* Add "useUrlParams" to requestConfig
* Add config.methodsThatUseUrlParams
* Add methodsThatUseUrlParams config tests
* Don't switch to body params based on extension
