https://htmx.org logo
Join Discord
Powered by
# 🔥-django-htmx
  • h
    but every other field should filter on change?
  • h
    what do you currently have for your hx-trigger
  • h
  • c
    The solution i can think of: Listen the event when datetimepicker is being closed, in this listener do an hx-get request
  • e
    Thanks that's what I did.
  • f
  • f
    This puts 
    tables2
    to a completely different level!
  • g
    Ho, someone has already managed to load a datatable with htmx in django, I haven't done it yet, I read somewhere that with htmx.process() but I don't know how to apply it to the datatable
  • p
    Is it expected behavior that HTMX requests should fail to handle responses with >= 400 status codes? I'm trying to render a login form with re-populated form values and a "Failed authentication" message. It works great (from Express) with 
    res.render('/my/handelbars/partial', { myValues })
    -- but if I include the 403 status, it fails to swap out the form completely (just doesn't swap anything as though the request failed). Only difference is changing above to: 
    res.status(403).render('/my/handelbars/partial', { myValues })
    -- How can kick back a form with errors and an appropriate status code?
  • m
  • p
    Oh that helps -- at least now I understand why it's happening. I still feel like I'm not getting something though. I have to write a separate JS block to allow for "forms-with-errors" to be displayed with correct status code? Perhaps I'm approaching this wrong. I really wish there some examples out there of basic CRUD patterns. I so love this concept but I'm struggling to figure out the basics.
  • m
    we treat 400 response codes as errors that will not swap, which is usually what you want. Unfortunately there isn't a spec on HTTP status codes we can follow, so we paint with a broad brush and allow users to override the defaults we picked with a bit of scripting.
  • m
    I agree a "CRUD for X" where X is "django, flask, php, etc." would be great
  • h
    is this perhaps not a django form? Django will return a form response as a 200 if it's invalidates
  • p
    Actually, even higher level than that (your patented HOWL stack 😜 ) -- just a guide to understand the basic pattern to submit a form, handle success and redirect, or repopulate form with errors and status code. Figuring out the backend part can be left to the user. I just need to understand the pattern.
  • m
    can you respond w/ a non 403?
  • m
  • h
  • p
    @hundreds-camera-24900 Maybe I'm being pedantic but submitting a login form with bad credentials feels like it should be a 403 and not a 200.
  • h
    no, a 403 means the request is denied
  • h
    you have an allowed request with data about the failed attempt
  • m
    you are welcome to do that, but you'll need to teach htmx what that means unfortunately
  • p
    hmmmm.... Okay, that sounds reasonable. Maybe I just need to send 200's and get on with my life 🙂
  • m
    Copy code
    js
document.body.addEventListener('htmx:beforeSwap', function(evt) {
    // render 403's for login failures
    if(evt.detail.xhr.status === 403){
        evt.detail.shouldSwap = true;        
    }
});
  • h
    It's a little tricky because you're expressing application level behavior in an http status code
  • h
    rest as a structure is cool because it mixes the two
  • m
    I am not doctrinaire about response codes and have seen lots of people do lots of different things so... pluggable
  • p
    can you tell I'm coming from a REST API background? 😉
  • h
    yes 🙂
  • m
    we are inventing the future of HTML hypermedia here folks, let's give ourselves some leeway!
1...565758...100Latest