Is there something for IntelliJ ?

not yet!

<a
  href="/publications/"
  hx-vals='{"page": 5}'
  hx-target="#list"
  hx-swap="outerHTML scroll:window:top"
  class="page-link"
  aria-label="Next Posts">
→
</a>

on a boosted link aught to...scroll all the way to the top, right? It seems to be scrolling to the top minus the height of my navbar. EDIT: Looks like using

show:window:top

works correctly, but's also scrolling to the top, I figured the

show

modifier just jumped to the top

Hi, folks! Has anyone run into this issue? I searched the docs and older posts, but found nothing. Every time I use hx-get, I'm not getting the query params in request.GET, which is always empty after I submit the form. Without htmx (submitting the form through traditional method='GET'), I can fetch the params just fine in the backend. The only way I can get the params through an hx-get is to specifically add the form field in hx-include. Is it not standard/default behavior for hx-get to send the query params through request.GET ?

Here is my form:

<div>
        <h2>TEST GET</h2>
        <form>
            Random text: <input type="text" name="inputtext">
            <button hx-get="{% url 'teste-get' %}" hx-target="#texto-alvo" hx-include="[name='inputtext']" name="botao-envio" type="submit">Enviar</button>
        </form>
    </div>
    <div id="texto-alvo">
        <p>Change this text.</p>
    </div>

If I don't add the hx-include tag, request.GET is an empty .

From the docs: > By default, an element that causes a request will include its value if it has one. If the element is a form it will include the values of all inputs within it. I guess you have to put hx-get on the form?

Thanks a lot! It worked fine by putting the tag on the form. I guess I've been doing this wrong with POST requests too, by putting the hx-post tag on the submit button. Don't know why, but for POST requests, it works that way.

is there something like hx-after='some_javascript_code()' that would run after the request and swap ?

we use events rather than attributes for the events, and rely on things like Alpine, hyperscript, vanillajs, etc. to do the code part

this was a design decision when moving from intercooler.js, to keep the core of htmx simple

thank you

I've got a page mostly implemented with htmx, but inside that page there's a couple of third party javascript components (for example an autocomplete input) which need to talk to the backend in json. So on the backend side, all endpoints generate html (for htmx) except for two endpoints which generate json (for the js components). Mixing html and json on the backend doesn't feel right to me, am I following a wrong approach?

i am pragmatic about this: if the elements are self-contained and require JSON and do what you want, just use them

@User is using TomSelect for some cases in his htmx-based app and I fully endorse it

w/ a simple JSON API, it's much better UX than what could be achieved w/ pure htmx

Yeah just recently started using Tomselect and it’s pretty nice. It’s a lot saner (and dependency free!) than select2. I have it spit out html to the backend and consume a json response from the server because it’s easy enough for me to emit json in this case from the backend, but it’s got a hook if you want to respond with html and then transform it into what it needs client side.

I feel this pattern doesn’t violate htmx principles too much 😁

I was planning to use tomselect this way too. Good to know. But it does feel like I'm violating some principles 😨

Because in mind head there is a little voice that says "you're now spitting out json in some places, just spit out json everywhere for consistency"

consistency is the hobgoblin of normie minds

principles that cannot bear being violated are not good principles

* except for this principle

I am confused by the form validation example given. What is HTMX expecting to post the form?

Plenty of interaction SHOULD happen on the client. This is a great example. Just think of it as a polyfill for the existing underpowered select box. Same for WYSIWYG controls, and other front end widgets. Now, once you’ve chosen the values in the form, REST demands that the value should be POST-ed to the server instead of being “saved” in a client-side JS/NOSQL “database.”

has anyone actually used https://hyperview.org/

I am so curious to hear how it worked for someone

This kinda sounds like how (some parts of) Apple's tvOS view layer works: https://developer.apple.com/documentation/TVML

I use tomselect without any JSON.

html
              <select :id="$id('select-payee')"
                      name="payee"
                      autocomplete="off"
                      x-init="new TomSelect($el, {create: true, selectOnTab: true, maxItems: 1, onOptionAdd: (value, data) => { $dispatch('optionAdded') }});"
                      hx-target="this"
                      hx-trigger="optionAdded delay:50ms"
                      hx-params="payee"
                      hx-post="{% url 'add_payee' %}"
              >
                {% include 'partials/_payee_select.html' %}
              </select>