https://htmx.org logo
Powered by
# htmx-general
  • m
    rails forms are pretty good
  • w
    My only experience is with Django forms, but I can give it a thumbs up
  • w
    There's also a django package crispy-forms that some people use that might be worth looking into if you're going that route (makes it easier to implement Bootstrap styling, etc)
  • w
    On another note: Looking through the source code, what's the difference between an InlineSwap and..not an inline swap?
  • w
    is it the difference between innerHTML and outerHTML?
  • r
    Could you clarify slightly more? It seems like Rails has many ways of doing forms based on their docs
  • n
    Hi Everyone, I have a survey/form with two buttons, it will continue to route the user to a different "flow" depending on which button they click, eg. Yes, No, how do I capture which button is clicked with HTMX ? I'm looking over the docs and not finding it.
  • f
  • n
    Ah, I hadn't seen that one. This library has so much!
  • n
    I'll give that a try, thanks mate!
  • m
    they call them "form helpers": https://guides.rubyonrails.org/form_helpers.html and they are pretty good, dealing w/ checkbox issues, selects via reflection, etc. I also really liked simple_form when I used it: https://github.com/heartcombo/simple_form
  • r
    Interesting, thanks for the info!
  • h
    I have done a lot of form work - I like django except for the decoupling between presentation and validation
  • h
    Django + floppy forms was my favorite exp
  • h
  • h
    I've also committed to https://schematics.readthedocs.io/en/latest/ which is similar to yup.js - ie validation outside of the context of a form
  • h
    generally I see them do some combination of: Generation of html for user interaction, validation of user data in client per field, validation of user data in client multi-field/as a whole, reporting error handling as user types, validation of user data per field server side, validation of user data server side multi-field/as a whole, reporting error handling back to user and keeping data state when attempting to save, and database saving logic
  • h
    idk if you're doing it from scratch it always helps me to put a framework in place first and figure out which of the cases you're going to tackle
  • r
    Yes I am doing it from scratch, this is super helpful!
  • h
    yeah makes sense to figure out what do you want to do and what do you want to use existing libraries for / out of scope
  • h
    EG formik doesn't do any data validation - it takes a yup schema (https://github.com/jquense/yup) and validates the data against that
  • h
    I don't love formik for other reasons (it's too hard to just say "this is a field I want data here") but yup has been great to work with, so I really liked that pattern
  • r
    Well Nim hardly has any other validation type libraries, so this will probably be the first one! I'm just doing validation, form generation, and serializing to a model/object. And the goal is to make it HTMX friendly without being coupled to HTMX specifically 😄
  • f
    choose Django and I will guide you~
  • f
    harhar
  • h
    so one thing Django does w/ forms that is intersting ( and this is pretty common actually now that I think about it)
  • h
    the form object doesn't actually touch the form tag
  • h
    just the inner fields
  • h
    so the django form explicitly doesn't handle the target or action pieces of the form
  • h
    or the submit button
1...506507508...1146Latest