https://htmx.org logo
Powered by
# htmx-general
  • s
    that graph is remarkably accurate.
  • s
    I'm constantly trying to less experienced devs that it is ok to write the same code twice or more, and in fact, you will likely end up with better code if you wait longer before building the abstraction.
  • s
    My personal rule is always to never build the abstraction until I have written the code at least three times.
  • m
    premature abstraction... we've all been there 😑
  • g
    But abstraction isn't just about reuse. That's a common mistake.
  • g
    It's about usability, not reusability. Reusability is just one type of usability.
  • s
    Right, but the point is that often, inexperienced developers will create abstractions before they have enough knowledge of the domain and this create an abstraction that doesn't fit very well with the eventual business logic that needs to go on top of it.
  • s
    aka. not accounting for the 'unknown unknowns'.
  • g
    i agree, but bad work is bad work, i think abstraction takes a lot of the blame for bad work when really you can do anything badly in this industry lol
  • m
    true story
  • m
    absolute 🔥
  • w
    I have a quick question about the Javascript API for HTMX. I have an old school jquery function which is currently doing a form post when someone clicks something by 1. creating a form 2. creating a bunch of hidden inputs within the form 3. submitting the form I'm now trying to replace this with htmx but still keeping the javascript function. I spotted htmx.ajax() in the documentation, but can't see a way of posting parameters other than encoding them into the URL. Is there a way to programmatically do a htmx POST request and pass it the parameters to POST to the URL?
  • w
    For example, in the documentation it gives me these options
  • w
    Basically looking for something similar to the options.params setting you can use in Unpoly's up.replace method, or an alternative way to deal with this sort of programmatic posting of specific data https://unpoly.com/up.replace
  • m
    unfortunately no, not right now
  • m
    the ajax method is still really focused on triggering elements in the dom
  • m
    but looking at the API, we can improve it to handle this use case
  • m
    (the javascript API emerged after the core htmx functionality was built, so it's still a bit rough)
  • m
    do you mind posting the current code so I can take a look at it and how we might improve the API to deal with it?
  • m
    Also, if you are brave, you might look at hyperscript, which surfaces the fetct() API
  • w
    I think it would actually be a nice improvement to the library. One of the nice things about Unpoly is that is has fairly "symmetric" functionality between the attributes on the html and the javascript API i.e. if there is an attribute up-visit there is also a javascript method up.visit() which allows you to do the exact same thing through javascript
  • m
    yep, that sounds reasonable
  • m
    if you can give me a gist or post the code, I'll see what we can do w/ the API
  • m
    I hope to cut a new release of htmx and hyperscript next friday, so it could make that release
  • w
    Yes. No problem.
  • w
    Okay, so current code looks like this (this control was written a loooooong time ago, hence not using jQuery for this kind of thing!)
  • w
    So the idea is relatively clear - all our reports have links on them which allow ordering the report by relevant columns. This method takes various parameters to do with the report and submits them to the server which then redirects back.
  • w
    With unpoly I was able to rewrite this like this
  • w
    So basically it just says "replace the body of the page with whatever is received back when you post the following parameters to this URL"
  • w
    At the moment, we're just evaluating a few things to make some bits of an old product a lot more reactive without including all the complexity of webpack / vue / react etc so there is no need to fit it into the next release. Just thought I'd a) ask the question and b) provide a use case for why people might want to do this.
1...167168169...1146Latest