https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    @User I'm starting to dig out from under the avalanche and review pull requests. I haven't gotten up the courage to look at the SSE stuff yet, but should get to it by the end of the week.
  • g
    That's cool. I'm glad to hear that life is getting under control. All the SSE code can wait until you have a nice chair and desk set up.
  • w
    🎙 devMode podcast episode 85: "Sprig brings Reactivity to Twig" is out! 🌿 https://devmode.fm/episodes/sprig-brings-reactivity-to-twig
  • w
    ^ uses htmx, and is mentioned a bunch @User
  • b
    @User Top of my wish list for hyperscript is for it to self-initialise. Why require people to output 
    _hyperscript.start();
    ? (when not used with htmx)
  • m
    short answer: it should self initialize
  • m
    long answer: I am building the compiler in a somewhat experimental way where you can add new expression and statements to the language, and I wanted an "OK, the language is done" spot.
  • m
    but that isn't the common case, so it should self init and make the uncommon cases possible
  • m
    @User ☝️
  • b
    Ah perfect!
  • m
    @User @User great interview, just relistened
  • w
    Thanks @User -- yours comes out next Monday!
  • m
    awesome
  • b
    > short answer: it should self initialize @User Perhaps the quickstart section of the docs could use some TLC 😉
  • m
    yeah, when I say it should, I mean in a future release
  • m
    by the end of september, for sure
  • m
    currently figuring out where in my schedule this work is gonna get done
  • m
    thinking about it: htmx shouldn't need to know about hyperscript at all
  • m
    hyperscript should plug in to htmx events instead
  • m
    I'll need to work that out over the next few weeks
  • m
    but hyperscript should be listening for the load event
  • b
    Thanks for the clarifications and keep up the excellent work @mysterious-toddler-20573 !!
  • m
    I am having an issue with the 
    htmx:afterRequest
    event not getting triggered, even though it shows up with 
    htmx.logAll()
    . Similar to what it's mentioned here https://github.com/bigskysoftware/htmx/issues/79 I am using this to test:
    Copy code
    js
htmx.on('htmx:afterRequest', () => console.log('htmx:afterRequest'));
    Is there another way to get this working or is it still an issue?
  • m
    I tried it with an extension to see if it made a different, but no.
    Copy code
    js
htmx.defineExtension('test', {
    onEvent: function (name, evt) {
        console.log(name);
    }
}
    Only these show up:
  • m
    htmx:configRequest htmx:beforeRequest htmx:beforeOnLoad htmx:beforeSwap htmx:afterSwap htmx:processedNode htmx:processedNode htmx:load htmx:afterSettle
  • m
    Here's my interim solution for doing something after the request is complete.
    Copy code
    js
htmx.on('htmx:beforeRequest', (event) => {
    let xhr = event.detail.xhr;
    const onload = xhr.onload;
    xhr.onload = function (callback) {
        // do something
        onload.apply(this, arguments);
    }                
});
  • m
    is your swap an outerHTML ?
  • m
    I wonder if we are firing it on the node that was swapped out, rather than the node that was swapped in
  • m
    No, it's innerHTML
  • m
    Btw, here's oob swapping in action. Very cool!
1...202122...1146Latest