https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    yeah, look at the package in /www/package.json
  • m
    eleventy-plugin-sass
  • m
    although it might rely on sass being installed :/
  • m
    i really hate sass
  • m
    less should have won
  • m
    the event info would be a plugin, yes
  • g
    Ok. I’ll work it out from there.
  • g
    Is it wrong that I just prefer straight CSS? These tool chain guys really grind my gears 😉
  • m
    i tried straight css for a while, but eventually gave up and went back to SCSS. Less should have won. I'm convinced that the bootstrap change to scss was due to personal lobbying rather than technical merit.
  • m
    OK
  • m
    so
  • m
    @User and anyone else w/ an opinion
  • m
    I have implemented general event filterins with the 
    [arbitrary expression]
    thing
  • m
    I'm not unhappy with it
  • m
    but I wonder if it's a little too general
  • m
    and we'd be better off with something more like the css attribute selectors: https://www.w3schools.com/css/css_attribute_selectors.asp
  • m
    any thoughts on the current syntax?
  • b
    @User Just coming back to htmx after some time away so trying to catch up on the developments. Is this the current syntax you have for event filtering?
    Copy code
    html
<!-- Trigger a htmx request if the keydown event was caused by the `enter` key and the element's value is not blank -->
<div hx-trigger="keydown[key=='enter' && elt.value!=='']" ...>...</div>
    Switching to CSS selectors would require writing a parser that can deal with all of the CSS attribute selectors (I assume), and keeping up to date with developments in CSS. So the simpler and more powerful approach would seem to be evaluating the JS expression as you are now, and since this is more of an advanced use-case, the lower level approach seems acceptable. https://developer.mozilla.org/en-US/docs/Web/CSS/Attribute_selectors
  • b
    Perhaps @User, @User, @User have some opinions too?
  • m
    @User yep, it's general javascript expression validation
  • m
    you can even do stuff like this:
    Copy code
    html
<div hx-trigger="keydown[['enter', 'escape'].indexOf(key) >= 0]" ...>...</div>
<div hx-trigger="keydown[myValidationFunction(evt)]" ...>...</div>
  • m
    I am getting more OK with it
  • m
    The lexer isn't too complicated, and it is pretty damned general
  • m
  • l
    I think, as you get older, you've had to maintain several systems and come to appreciate how "clever is not helpful" unless it's very well explained and heavily tested.
  • b
    @User I'd lean towards what you have now over using a CSS attribute selectors syntax, for which I can see feature request after feature request for adding more flexibility being submitted.
  • l
    There is an advantage of a limited DSL, that is, you know that the code won't be calling other functions or doing irregular things. That said, flexibility is nice.
  • b
    In general I agree, however 
    eval()
    is already being used in other parts of the code...
  • m
    I'm pretty proud of the fact that we only call eval once per conditional expression 🦾
  • m
1...535455...1146Latest