https://htmx.org logo
Powered by
# htmx-general
  • h
    yeah
  • h
    just some kind of tenant id
  • a
  • h
    yeah I was just reading that
  • a
    I’m looking to build an internal dashboard app so mostly just reading data. I really like the idea of HTMX so I am thinking of HTMX, Tailwind, handlebars (for transforming the JSON to HTML, and Postgrest). That should give me the whole stack.
  • a
    Any thoughts on if I use js-cookie for storing state instead of HTMX or Alpine as mentioned above?
  • h
    https://htmx.org/extensions/client-side-templates/ for the rendering is a good one to have in your pocket
  • a
    State just being the JWT.
  • a
    Yes, was planning to use that for handlebars. Unless you recommend one of the other 2?
  • h
    I like nunjucks because it looks like jinja/django templates which is my default choice
  • h
    I don't think it's worth having a strong opinion there tbh
  • h
    another option is to render fully with alpine and https://htmx.org/extensions/alpine-morph/
  • a
    Hrm, will check that out, thank you. I’m weakest in JS so for now I really only need a way to remember the JWT. Not planning to do any other interactivity right away.
  • h
    I think a cookie is fine
  • h
    you could also do local storage
  • h
    I would probably go with a cookie all else equal becuase it's simpler
  • a
    Noted on nunjucks, will read those docs before I start development on Monday. Thank you so much for this information.
  • a
    Simple is what I want right now. I’ll figure out how to parse the JWT out of the JSON, maybe I can do it with handlebars and save using the js-cookie library.
  • a
  • h
    yeah it's neet
  • h
    I was googling that, it's new to me
  • h
    I've always jsut done a little custom thing
  • a
    I typically don’t like adding dependencies or libraries if I can do something little myself but in this case I need to finish by next Friday so sacrifices must be made. 😎
  • a
    Thank you again!
  • b
    Ah ya sorry for the long-winded repeat hah. Definitely saying the same thing. Glad you got it
  • j
    Yr not a dummy. We all stare at code too long sometimes and get stuck.
  • r
    This comes up far too often and should get added to the cookbook.
  • r
    Been thinking of a page on "interception" / "pausing events" in the Hotwire to HTMX migraton guide, but I really do think some common practices such as this warrants its own page in the manual--- See:
  • r
    A first pass on this:
  • r
    (See events section)
1...683684685...1146Latest