https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • s
    I was in Java world my first decade of programming, used JetBrains. Then got tiered that my laptop battery was dying In a few hours and tried vscode. I’m very heavy shortcut user, so I was expecting that there was no way I could switch away from JetBrains. But it happened quiet quickly and very easily. For 1-2 weeks
  • m
    understand, but I will say two things
  • m
    1) jet brains supports open source work in what appears to be a genuine manner
  • m
    2) if you don't pay for a product, the product is you (to an extent)
  • m
    in general, I try to pay for my tools if a good underdog option is available
  • m
    (not judging, this is just my philosophy)
  • m
    narrator: he uses github
  • m
    😑
  • g
    In general, yes. If you're not paying for it, then you're the product. But I prefer to think of VSCode as a loss leader... in a standing-on-the-street-corner "the first dose is free" kind of way. MS reeeeeeaaally wants you in their developer and cloud ecosystem, and they're willing to give you LITERALLY THE BEST DEVELOPMENT TOOL AND I WILL FIGHT YOU OVER THIS FACT for free.
  • g
    snorts another bump of VSCode
  • m
    are you aware that it is written in TYPESCRIPT?
  • m
    checkmate
  • b
    Hey @mysterious-toddler-20573, any thoughts on my one-liner PR that helps simplify htmx template responses? https://github.com/bigskysoftware/htmx/pull/1235
  • m
    seems like a breaking change, iirc someone requested the opposite feature at one point
  • m
    i have to say, I feel like I haven't gotten oob swaps quite right yet
  • b
    yeah I've noticed that the oob-swap feature is discussed a lot here
  • b
    in my opinion, the oob swap feature should be simple. if you want to swap something that the request isn't targeting, put that element in the root of the response. if "oob-swap" shows up elsewhere just ignore the attribute. if you want a more involved tree diffing/merging solution then use one of the more advanced extensions
  • m
    if only extensions were easy to write and build your own version paying only for the features you choose.... 🪄
  • m
    made worse by the finicky nature of table element parsing (behold, the horror: https://github.com/bigskysoftware/htmx/blob/master/src/htmx.js#L267
  • m
    it is sadly very hard to parse arbitrary HTML content
  • b
    yes I was going to mention that html tables throw a bug ugly wrench into the "simple oob swap" concept
  • m
    this becomes particularly true in htmx 2, if we support parsing entire documents (for head merging support, see idiomorph: https://github.com/bigskysoftware/idiomorph/blob/main/src/idiomorph.js#L305)
  • m
    😑
  • m
    I think template tags are the answer here, but I need to think about it more
  • m
  • m
    sometimes I sits and thinks
  • m
    and sometimes I just sits
  • b
    I briefly looked at template tags before and they seem... abstractly interesting (?), but I couldn't see how they would be useful to htmx specificially
  • g
    They parse their contents in a way that avoids a lot of the pitfalls of 
    DOMParser
    and 
    createHTMLDocument
    . For example,
    Copy code
    html
<template><td></td></template>
    will successfully create a element -- and nothing more -- in the template's 
    .content
  • b
    oh that's handy
1...104210431044...1146Latest