https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • m
    I'm adding fragment support to golang's QuickTemplate (by Valyala)
  • m
    I guess I can just do it stack based and scrub fragments statements in fragment sources after the fact
  • m
    that works
  • m
    and it's simpler
  • c
    Its great lib and it has theme system so yup, its prolly top tailwind ui lib and ye theyre limiting the boilerplate classes
  • c
    theres so many ui libs for tailwind tho
  • c
    it depends what do you need
  • c
    Im more into making components from scratch tho, but it depends
  • m
    👍
  • m
    for each fragment with a fragment do you need to include the parameters of the previous fragments and parent if you want to use it?
  • m
    in the definition?
  • m
    this is a tricky part
  • m
    do you pass parameters in as a map?
  • m
    Or are they strongly typed?
  • m
    strongly typed
  • m
    it's generated code
  • m
    more specifically I'm adding fragment support to https://github.com/valyala/quicktemplate
  • m
    I think If I use any variable it would have to be in every outer scope
  • m
    OK, so that's a bit hard
  • m
    what you need to do is analyze the scope for used symbols, and those become the arguments to the template
  • m
    Copy code
    @parameters(users: List<User>)
<html>
  <ul>
    #for(user in users)
     #fragment example
       <li>${user.email}</li>
     #end
    #end
   </ul>
</html>
  • m
    this is a made up templating language
  • m
    but the right thing for the inner example fragment is to have a single implicit argument, 
    user
  • m
    even though 
    users
    is in scope
  • m
    😑
  • m
    this is one area where dynamic languages are way easier
  • m
    to do it right, for statically typed languages, you'd want to look at symbol usage rather than availability within a fragment
  • m
    I mean I could just add the parameter manually like this:
  • m
    Also possible
  • m
    but annoying
1...809810811...1146Latest