https://htmx.org logo
Join Discord
Powered by
# 🔥-django-htmx
  • h
    the most obvious case of this is "load a form page, if it's an htmx request the form is being submitted so only return the form itself, if it's not an htmx request then it's a fresh request and give the site chrome back"
  • h
    so right now my usecase for the hx-retarget view is
  • h
    form page "anime-create" and detail page "anime-detail" - anime create form checks if it's an htmx view and if it's not gives a fresh form + site chrome
  • h
    if it is, give JUST the form assuming the form is being submitted and needs validation
  • h
    if the form is valid, then issue a 302 to "anime-detail"
  • h
    and the old issue was the anime detail showing up in the slot where the form would go for validation - that is now fixed because anime-detail includes the hx-retarget header
  • h
    but that means that anime detail will now ALWAYS be full page
  • m
    why issue the 302?
  • h
    that's Django's normal behavior
  • m
    Why not render the template directly?
  • h
    form submits w/ a post, 302 to a "success url"
  • h
    because it's pretty annoying tbh 😦
  • h
    that would be abetter solution
  • m
    🤔
  • m
    OK
  • h
    because it's a single request so obviously more efficient
  • h
    but django cares deeply about http verb in a lot of cases
  • h
    so if you post to view a, and then want to call+return view b you'd need to synthase a fake request to act as the get request
  • h
    or you have to duplicate the work to get the context of view b so it can be called directly in the form_valid response from view a
  • h
    either way you either need to do a lot of work to fake a request, or move the work that normally lives in the views to reuseable functions
  • h
    which is possible but not ideal because it's not "django-y"
  • h
    this is 100% not htmx's fault it's just an artifact of django wanting all form submits to act the same way
  • h
    so wrapping it back to the header, view b is forcing a full body load, which will work great until for some reason I want to add a form to that page and self submit or something
  • h
    I think I'm overthinking this
  • h
    I think the answer there is obvoiusly just make a new view that only handles the form submit
  • h
    the detail page is locked at being detail and won't mutate in the future to being a create/update view, and if you DO need that case just move it over to the side and handle it separately
  • h
    and the same hx-retarget will work for that submit the same way it will for the first view
  • b
    I didn't read all the details but so far I've created a view specifically for handling the form submit and its worked really well
  • h
    That's where I landed too - don't try to do too much with a view
  • v
    Having a larger number of smaller, specialized views is the way to go with Django + htmx
1...181920...100Latest