nor borrowed from there

Well, it isn't quite working. The query param doesn't end up getting sent to the server when I have it bubbling up to the wrapper.

html
<div
             hx-get="/fwa/set-schedule-type"
             hx-target="#workSchedulePartial"
             hx-swap="outerHTML"
             hx-trigger="change">

            <div class="form-check">
                <input class="form-check-input" type="radio" name="scheduleRadios" id="scheduleRadios1" value="STANDARD" checked>
                <label class="form-check-label" for="scheduleRadios1">
                    Standard schedule: Designated work hours that set typical start and stop times for a unit's employees.
                </label>
            </div>
            <div class="form-check">
                <input class="form-check-input" type="radio" name="scheduleRadios" id="scheduleRadios2" value="FLEXIBLE">
                <label class="form-check-label" for="scheduleRadios2">
                    Flexible schedule: Descriptions for types of flexible schedules can be found at the <a href="https://hr.uiowa.edu/well-being/family-services/workplace-flexibility/types-flexible-work-arrangements">Workplace Flexibility website</a>.
                </label>
            </div>
            <ul>
                <li>Compressed work week.</li>
                <li>Adjusted start and stop times.</li>
                <li>Flexible based on demand. No set or stop times.</li>
            </ul>

        </div>

Ah, do you have it wrapped in a form?

Is it possible to do the following without JS, only relying on attrs? While request is in flight, start polling to some endpoint every X secs and stop when process is finished?

I suspect that it is achievable if you're sending some element with each request, like in progress bar example... Thought it can be simpler.

Okies, managed to do it with

hx-trigger="revealed, every 1s"

on loading indicator - now to think how to stop the polling, without 286 response code. I.e. when element (the loader) disappears, ideally it should be able to stop polling. But it continues...

Oh well... It came up that I can't send responseCode being 286, as it is a non-standard code, and i.e. Slim PHP Framework, that refers to IANA http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml specs, returns 500 error, because code 286 is not listed in specs...

This was unexpectable for me >.O

Oookay, it seems that you must return the custom undeclared HTTP codes with some statusText. Didn't know that... But still, I am doing something quite not right, as the polling still continues after I got 286

Figured it out. It must be the same element that started the polling to recieve such stop-code... I thought there is some global "hey stop you all pollers". Gaining knowledge is hard but enjoyable xD

🙂

you are pushing it hard!

please keep notes and keep adding to that pull requests where you think more docs are required

I wonder, is it possible to stop the polling globally for all elements, by receiving 286 code from any request? Let's say I have 2 active polls going, and I do not know when I need to stop them. But when certain event happens, I would do

hx-get="/api/cancelpolling"

where the response will come purely with this 286 code. And it will stop all the active pollings that are going on any elements...

As a learning exercise, put together a demo for hx-swap attribute values here https://hx-swap-demo.herokuapp.com Code: https://github.com/rajasegar/hx-swap-demo

that is fantastic

any chance you would merge it into the main docs repo?

@mysterious-toddler-20573 yes, it's wrapped in a form

it should include the values of all inputs in that case

If I put the hx-get directly on each input it works, but is a bit clunky. If I bubble it up the request is made, but no params make it to the server.

Is it that all values should be included if the form is submitted, or should htmx submit all values if the elements are wrapped in a form?

Because at this stage the form has not been submitted.

ah, this is a GET

w/ GET we do not automatically include the form values, you need to be explicit

so use

hx-include

(we don't include the closest enclosing form w/

GET

since links inside forms don't include the values)

you can use

hx-include='closest form'

(sorry, been thinking about hyperscript too much, should have recognized this earlier)

No, problem. Just pulled up the hx-include documentation. That should do it. I'll test it out this evening. Driving out of town today to get vaccinated.