Suggestions on how to proceed getting hx-swap-oob to support all hx-swap functionality?

[aral]

I need to get hx-swap-oob to support all hx-swap functionality (delayed swaps, etc.) so things like CSS animations can be used with WebSocket-based workflows and not just Ajax (see #2308). Basically, I need WebSockets to be a first-class citizen in htmx as Kitten now has a very sleek WebSocket-based workflow for building web apps, powered by htmx.*

As I see it, this requires quite extensive (though not necessarily complex) refactoring of the code. Most likely to make swap() a special case of oobSwap() and ensure that both handle delays, settling, etc.

I can see that work is ongoing in the v2.0v2.0 branch. I’m not sure how close that is to release so my question is:

1. Should I take this on or would someone more intimately familiar with the code want to do it?

2. If I do, I’m assuming I should implement it based on the v2.0v2.0 branch. Is my assumption correct?

3. Any other thoughts, approaches, etc., welcome (as well as feedback in case I’m missing something).

Thanks! :)

CC @1cg

* In the linked-to example, the connect attribute gets translated to ws-send and the existence of the onConnect() handler results in the necessary htmx and htmx-ws imports and related attributes being automatically added to the page. And the data attribute is an alias for hx-vals. All the regular htmx attributes can, of course, still be used – this is just some syntactic sugar that’s transpiled into regular htmx by the server.

[aral]

I’m assuming everyone’s busy preparing for the 2.x release.

I really need hx-swap-oob to support all the functionality that hx-swap has for Kitten so I’m going to go ahead and undertake this in my own fork.

Given it will require major changes to core elements, I will try to implement them as cleanly as possible but I understand if this means I’ll have to hard fork the project and inline it into Kitten in the future. Ideally, I’d like to avoid that but since I don’t know what the htmx team’s thoughts are on how to implement this, all I can do is implement it the best way I can and hope it fits for htmx’s plans for the future.