Feat/hx reselect support unset - #3153
Conversation
Telroshan
left a comment
There was a problem hiding this comment.
Yeah, makes sense to me to have the header replicate the attribute's potential values, including unset
|
I'd like to express my support of this since it will also allow |
|
In case I'm missing something I have to do to get this merged, please tell me. I'd like to think I'm "experienced" by now, but a lot is still new to me :). |
Don't worry, just continue to be patient. The "ready for review" label means you're doing well. |
|
@oliverhaas nothing on you, i'm just old, busy, tired and extremely lazy. thanks for your contribution |
Description
HX-Reselectcurrently does not supportunsetlike the attributehx-selectdoes. I think an htmx user would expect that, and for me it is quite handy to have that feature.I hope it is okay for me to open a PR to illustrate the linked issue, since it's somewhere in-between a feature and a bugfix I would say.
Corresponding issue: #3152
Testing
Basically already using this in one of my projects to have server-side rendering of redirects.
If the server would trigger a redirect, I just render the response of the redirected view and use
HX-Reselect,HX-Retarget,HX-Reswapfor swapping. Saves me one round trip and let's me use redirects more freely. And for full body swaps I need to useunset.Checklist
masterfor website changes,devforsource changes)
approved via an issue
npm run test) and verified that it succeeded