https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • t
    I like the escaped html entities in the name
  • m
    Lfg
  • a
    can't chameleon offer some of that? IIRC it offered an "almost 100% python" syntax for their templating (hopefully I'm not thinking of a different template engine). Unless I am misunderstanding what you mean.
  • a
    (we might have to move this discussion to #941388608290574336 )
  • m
    still thinking hard about this
  • r
    Suggestion, make this configurable. Teams who want to turn it off, can then do so, keeps backwards compatibility.
    Copy code
    html
<script>
htmx.config.inheritanceEnabled = false;
</script>
  • b
    That’s a good idea. It could be nice to have more granular control as well as that catch-all option, like 
    htmx.config.inheritanceEnabled.swap = false
    or similar
  • r
    Side benefit of config option: If we ever disable inheritance by default, reverting back to the original behaviour would be simple. Although I personally do think it's a great thing for newcomers/onboarding... keeps friction down, and its intuitive as heck....but option for teams to graduate to a more explicit mode.
  • r
    Neat idea as well.
  • b
    Yeah I like that. Inheritance definitely isn’t a bad thing, it’s more just how is best to keep track of it
  • b
    IDE support would help with that I guess. Imagine hovering over an element and being able to see a summary of its hx- attributes
  • h
    yeah would make for a nice chrome plugin too
  • s
    my 2 cents: Inheritance is for avoiding duplication, which might be nice in some situations but is not necessary. Much worse, to me, is confusion because of the added complexity, for me or for whoever has to maintain my code later. The duplication is not as big a problem with Htmx as it would be if I was writing JS, since I have other very nice ways of avoiding duplication in my favorite server-side programming language. So if I could disable inheritance, I would.
  • m
    I am currently thinking something like this:
    Copy code
    html
<div hx-target:inherited="this">
  ...
</div>
  • m
    where inheritance is explicitly declared on elements
  • m
    rather than auto-inherited
  • m
    still thinking
  • r
    Another idea: If 
    htmx.config.inherit = false;
    then you can explicitly turn on inheritance for specific properties using 
    <div hx-target:inherit="this">
  • r
    keeps the verbosity down until you need it.
  • r
    takes care of the whole "granular control" thing @blue-ghost-19146 was talking about, without having tons of config options.
  • r
    eithers good really, but would love to see inheritance stick around as the default, the feature has merit of being intuitive as heck.
  • m
    yeah, I'm still on the fence about this
  • m
    it's a major shift and I don't hear a ton of complaints, but the ones I do are often very loud
  • r
    Yeah
  • r
    At the moment there isn't any convenient way to turn it off for the entire page? just 
    hx-disinherit
    on a specific element..
  • r
    Could have 
    <body hx-inherit="false">
    for some consistency with the 
    hx-boost="false"
    API.. but I bet people really using htmx are setting a few 
    htmx.config.*
    already anyway... I am.
  • r
    Making it work like the boost API might be nice.
  • r
    I think your idea may be less verbose for the level of granularity though.. It may be a question of which one is more valuable: A) full inheritance with explicitly turning off specific attribute inheritance. B) zero inheritance with explicit turning on specific attribute inheritance.
  • r
    with this you almost get the best of both worlds. Full inheritance or B)
  • b
    Yep, I like the idea of inheritance remaining by default, but able to be disabled (either similar to boost or through config). If disabled, the 
    hx-target:inherited=“this”
    example would work nicely to give granular, explicit control over inheritance
1...741742743...1146Latest