https://htmx.org logo
Powered by
# htmx-general
  • h
    django-components works by writing an object, then you decorate the object with @component
  • h
    and then when you render the component you have access to methods/data/scope that are component specific
  • h
    so much closer to what a component means in terms of react/vue/whatever
  • h
    but the template language for it is (imho) not as good as slippers
  • f
    So if you'd have to choose, you'd go 
    django-component
    ?
  • f
    Curious to see how they affect template rendering time. After all the default template rendering benchmark is quite good.
  • h
    yeah because I want a form component that checks the type of the field component and uses different template/sub component depending on type
  • h
    and afik you can't do that in slippers
  • h
    I haven't benchmarked personally but
  • h
  • f
    I see. Well so far I'm ok with the regular 
    {% include %}
    and htmx fragments. But maybe that's just because I didn't get the taste of what actual components can do.
  • h
    you can delegate a lot more logic to render time in a structured way
  • h
    like a good example would be a UserIconMenu in the top right
  • h
    with first class components you could drop that in
  • h
    and then the component itself would see if the user is logged in, and if so check if they have an avatar and use that vs the default one
  • h
    or hit the DB to pull out the number of unanswered messages or something
  • h
    basically you can move state checking/fetching out of view and into components where they have tighter scope
  • f
    Mmm but how's that different from having an 
    {% include "user-menu" %}
    which then does all these checks?
  • h
    because then the view has to provide the data to the include
  • f
    Yeah well; 
    request.user
    is always included 😛
  • h
    yeah user is a bad example because it's ubiquitous 🙂
  • h
    but say it's like current open pull requests or something that's an orm query
  • f
    So how does the component pull the data then, if it's not part of the 
    context
    ? That now sounds like 
    templatetags
  • h
    yeah it's much closer to a template tag
  • f
    So why not use template tags?
  • h
    becuase they require a lot of annoying parsing logic
  • h
    compoenets are a halfway step
  • h
    you don't have to worry about like
  • h
    "is my tag {% foo %} or is it {% foo %} blash {% endfoo %}"
  • h
    template tags are technically more powerful than a component because they can make parsing decisions
1...508509510...1146Latest