https://htmx.org logo
Powered by
# htmx-general
  • m
    👍 will look at it in a few
  • m
    would a 
    HX-Replace-URL:
    response header satisfy your needs?
  • s
    Yes. And a matching attribute. I noted the idea in the issue
  • m
    I like the idea of 
    hx-push-url
    and corresponding 
    HX-Push-Url
    (we can support 
    HX-Push
    too until 2.0) to keep things standardized and then corresponding 
    hx-replace-url
    and 
    HX-Replace-Url
    as well, does that seem sane?
  • s
    Yup. That is very reasonable.
  • s
    The names hx-url-push and hx-url-replace (put 
    url
    at the front) would put them next to each other on the documentation, but otherwise probably isn't worth changing
  • g
    I love both of these headers. The OCD in me is happy when all the names line up between attributes and response headers.
  • s
    Would you like me to look into making a PR for the 
    HX-Replace-URL
    header/attribute?
  • m
    I am looking at it, I kinda want to combine that and HX-Push-Url into a single piece of functionality, but still thinking about it
  • m
    i'm old, so it takes a while
  • s
    Cool. No rush. Thanks for the great work!
  • c
    Hello there, I am quite interested on using htmx. What is your solution for css styling? Coming from React SPA + tailwind user 👀
  • r
    Tailwind is fine and is highly complimentary to LoB. Pereonally i use stylus (sass for minimalists).
  • r
    Hello everyone! I have a trouble with htmx. I have a page with some form which should be sent via htmx and content below it. When I send a form, only content below this form should be replaced with new content. However, it turns out that the content is getting replaced with an entire page! Can you please tell me how I can extract only the content from swap and place it instead of old content?
  • r
    This might be a general JS question, but is there a way to extend the json-enc extension to support arbitrary arrays and nested objects? Would it be possible to submit
    Copy code
    js
{key: {nestedKey: value}, values: [{fun: 'times'}]}
    I found https://stackoverflow.com/questions/7793811/convert-javascript-dot-notation-object-to-nested-object for expanding out the object, so I could make a form that would have "key.nestedKey" as the name. I can't figure out how to do the array though, something like "values[].fun"?
  • g
    the naming convention i know is 
    values[][fun]
  • r
    Hm okay, but do you know any way to convert that client side?
  • m
    look at the hx-select attribute
  • r
    Thank you, I found it!
  • m
  • w
    Any chance that GH #827 is on the roadmap for the next update? I can provide more context if needed, but unfortunately I'm not at all familiar with the History API, so not sure what else I can do to help.
  • m
  • m
    ?
  • m
    this one?
  • w
    Yep!
  • a
    in one hour I'm going to pitch htmx to my boss. Wish me luck.
  • m
    i am guessing that we are not storing the hash in the history entry, typically the hash is client side state so can you explain what's going on here?
  • m
    Is 
    /services/speeches
    not an option?
  • g
    fwiw browsers do store the hash in history
  • w
    Sorry, one second I'll respond but I'm in the middle of cooking
1...698699700...1146Latest