https://htmx.org logo
Powered by
# htmx-general
  • g
    it says 
    @data-my-attribute
    , from your previous message i see that the attribute you wanted to set was 
    @data-kt-dialer-max
  • u
    Sorry i copied it just to make sure it it was correct but forsgot to change it after that, but yes its still not changing the value not sure why
  • g
    Does it work if you do this in the console?
    Copy code
    js
_hyperscript(`set #output's @data-my-attribute to "test"`)
  • g
    Did it set the attribute?
  • u
    yes
  • m
  • m
    this is working for me
  • m
  • m
    updated version
  • m
    working fine
  • u
    Thank you @User and also @User
  • u
    Now working
  • a
    Will we be able to see it on YT or similar? And… break a leg! 😁
  • g
    hhhhhhhhhhh
  • p
    Just done with my presentation and one question came up that I don't know the answer to: what about error handling? What are best practises for handling errors?
  • t
    some answer here if you talk about showing error message. : https://htmx.org/examples/update-other-content/
  • m
    humpty-dumpty tier nominalism, but the entire culture
  • m
    The REST (Rpc Except w/a String Transport) Architectural Style - Dissertation submitted in partial satisfaction of the requirements for the degree of DOCTOR OF ACKSHULLY in Information and Computer Science by Mr. De Facto
  • m
    which kind of error handling?
  • p
    Not sure what they meant exactly I am afraid, but I guess if there is a 4xx or 5xx reply coming back?
  • l
    Question on https://htmx.org/attributes/hx-request/ - this states that properties are set with "a JSON-like syntax", but the example doesn't have braces on either side, like 
    hx-headers
    or 
    hx-vals
    does. Should it use those braces? And, as an aside, are the two options listed but not shown in the example (
    credentials
    and 
    noHeaders
    ) boolean values?
  • m
    all JSON-like attributes may omit the curly braces. Not sure on credentials and noHeaders, but I assume so 😑
  • m
  • l
    I'm guessing it's also OK to have them present? (I'm polishing up the view engine helpers; want to make sure I generate them correctly.)
  • m
    yep
  • a
    We used to have a bunch of mutation observers watching the whole dom ... we never had any problems with it. That said... we've cut down on their usage a bunch by watching for events rather using hyperscript
  • a
    Ok, time for a bit of show and tell! We've just added a command palette into our React app, so I thought I'd show you what a TRUE SPA looks like. You'll also see a bit of our async backend processing behaviour, complete with UI progress bars, individual list item status updates, etc.

    https://youtu.be/zHoAwVcSLdE▾

  • a
    Ok ok... just before @User has a heart attack - that ain't no React app ☝️😁 That's a good old traditional MVC Java app, powered by htmx and hyperscript 💪 All of the page loading and most of the JS UI widget behaviour is also driven by htmx and/or hyperscript. There's some gratuitous web socket usage to update the individual table line item statuses during the latter part of the clip ... but for the rest it's html fragments all the way, complete with URL pushing and history support (oh, and not a single full page refresh anywhere of course)
  • a
    (no idea why the video preview image isn't showing up 🤷‍♂️ )
  • h
    I think I found a documentation bug
1...427428429...1146Latest