https://htmx.org logo
Powered by
# htmx-general
  • r
    Is there some other benefit to the new`HX-Location` feature I'm missing?
  • r
    Also when this is all sorted, we (possibly) need a "hotwire equivalents" page in the docs. Common best practice for stuff that hotwire does out of the box, so we don't lose people to hotwire. htmx is just sooo flexible.
  • r
    Also would make far less friction for people migrating from hotwire to htmx.
  • r
    You really did do it, thanks!
  • r
    To get the ball rolling so we have a place to add stuff:
  • p
    Has anyone successfully used Alpine to watch file upload progress? 
    x-on:htmx:xhr:progress
  • p
    I'm having some trouble getting it working and would love to see some sample code if you have it.
  • r
    @billions-microphone-84331 Added section on handling form redirects. Noticed you were also discussing this related to hotwire.
  • r
    Preview so far:
  • m
  • b
    I have successfully used BEM and Tailwind with HTMX. The trick with BEM is to make your own classes, even if you could use the ID that you made for htmx. Otherwise you create an unnecessary coupling. My recommendation: Use BEM if you want to avoid a CSS preprocessor step, otherwise, use whatever you want. HTMX really doesn't get in your way. BEM has had this problem since its inception with accessibility, labels, scrolling anchors, and other native html features requiring the liberal use of IDs. It's really not an issue as long as you don't mix the purposes
  • a
    Hello! I am considering using HTMX for the first time and wondering what the recommend solution is for connecting and authenticating with an API? Planning to use handlebars.js for templating but having trouble finding how to do the authentication with the API and then maintain that for the logged in user. I will be using JWT for the auth.
  • a
    @jolly-kite-167 said basically the same thing. Made me feel like a dummy. Of course, the id can be fore HTMX to do its thing, and then use classes for styling! I'm always learning new ways to not overthink things.
  • m
    are you integrating with a third party API? Or is this the core app? for third party JSON APIs there will be no escaping some scripting, so we typically recommend something like Alpine for managing that state. For you core app, we recommend using a session cookie rather than maintaining a auth token explicitly.
  • h
    Session Cookie is easier for sure, but I've had luck setting a prerequest event handler that adds the jwt as a header
  • c
    example code or it never happened
  • h
    Copy code
    javascript
      document.body.addEventListener('htmx:configRequest', (event) => {
        event.detail.headers['YOUR_HEADER_HERE'] = <token>
      })
  • j
    That looks like a cookbook candidate.
  • h
    I do that for django's csrf token
  • c
    nice
  • a
    I was planning to use Postgrest to generate a standard API so I don’t have to use a backend framework like Laravel. I come from a database background originally, a lot of Oracle and MSSQL work so stored procedures, triggers, views and all of that. Postgrest makes it super easy to get JSON output from the database and I think I can develop very quickly with HTMX on the frontend.
  • a
    Awesome, thank you!
  • h
    I've always been curious with postgrest, how does it handle authentication
  • h
    you just use the db user table?
  • a
    You generate a JWT in the database and send it as a header. Yes, basically.
  • h
    how does that work for limiting access to data within a table, but not disallowing the table as a whole?
  • a
    Allows for row level security already built into the database. So API will never return data the user shouldn’t be able to access.
  • h
    huh I haven't really played around much with row level security in the db
  • a
    Just add organization or user ID to the data and limit with row level security.
  • a
    Or really any idea, could be project ID as well.
1...682683684...1146Latest