Thomas Eizinger
Thomas Eizinger
There is https://github.com/multiformats/rust-multihash/pull/289 now which is up-to-date with latest master.
> Type checking may not even be of tangible benefit for htmx (htmx has a nice test suite). Here is a recent example of a bug that would have been...
If that is the preferred workflow, I think it would make sense to run that as part of CI to make sure it doesn't get outdated! What is the reasoning...
Another benefit would be that you can make use of the module system and split up the current monolith into independent modules.
As a first time HTMX user, I am currently primarily relying on `hx-boost=true` and the lack of support for `formaction` and `formmethod` created some confusion. It actually makes things non-functional...
Actually, it doesn't work. `e.detail.triggeringEvent.submitter` is not defined for me.
The `submitter` event exists on the `FormSubmit` event if I add an event handler myself. It seems `htmx` is not passing on all attributes of the event to `configRequest`?
I found the bug and submitted a patch here: https://github.com/bigskysoftware/htmx/pull/1156
Another thing that needs to be dealt with is setting the correct content-type. ```js if (formMethod === 'post') { event.detail.headers['Content-Type'] = 'application/x-www-form-urlencoded'; } ```
> This can probably be closed. Thanks for landing support for this in main library!