https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • e
    maybe that's intentional
  • e
    Yes. I have had this thought multiple times in the few weeks Ive been using htmx
  • p
    quick question: is there some way to do 
    hx-indicator="none"
    (i.e. disable a default hx-indicator) ?
  • s
    Copy code
    html
<input hx-post="..." hx-indicator="#none">
<!--hidden div for invisible hx-indicator-->
 <div id="none"></div>
  • p
    sure...but just wondered if there was an equivalent to 
    hx-swap=none
    . I think 
    hx-disinherit
    might do the trick?
  • s
    No. The code works, no need to look for something more
  • p
    yes it works, seems a bit hacky though
  • p
    adding an element that's never used
  • s
    Don't worry:)
  • p
    yep 
    hx-disinherit="hx-indicator"
    works
  • b
    If you set 
    hx-indicator=“none”
    does it do what you want? The docs suggest that it’ll look for a 
    none
    element, which I’m guessing you don’t have?
  • b
    Hacky but for a different reason 😂
  • p
    yes. It raises an error in the console though.
  • b
    Ah. Fair enough.
  • s
    Hiding indicator and inheritance - those are orthogonal features. One shouldn't be solved by the other. If you decide to get rid of inheritence? (because of project coding conventions or because htmx 2.0 changes something), then your solution will break
  • p
    hx-disinherit works but it will apply 
    htmx-request
    to the trigger element (so careful with any css you might have)
  • s
    Yes you get the result that you want, but it's a side effect
  • p
    hx-disinherit will cancel any config set at a higher level, which is exactly what I want.
  • s
    You do you. If it's how you do the work, then I'm 100%. Everyone got his own style
  • p
    so yes, I might decide to get rid of inheritance, but in this particular project it's not a concern.
  • b
    Disinherit seems like the natural way to do this? It’s getting inherited which isn’t what you want so turn it off?
  • p
    exactly. It does exactly what it's supposed to, which is to cancel out (as opposed to override) anything you set at a higher scope
  • s
    Yeah it's a stylistic discussion now, I don't like those. Everything is good guys
  • p
    you can also just do 
    hx-indicator=this
    which seems to do the same thing (i.e. applies 
    htmx-request
    to the trigger element)
  • e
    For a form post
    Copy code
    html
<form hx-post="/post-form" hx-ext="json-enc">
  <input type="text" name="person[0][name]">
  <input type="text" name="person[0][age]">

  <input type="text" name="person[1][name]">
  <input type="text" name="person[1][age]">

  <input type="text" name="person[2][name]">
  <input type="text" name="person[2][age]">
</form>
    Is there a way to transform the json like below before posting?
    Copy code
    js
{
  person: [
    {name: "", age: ""},
    {name: "", age: ""},
    {name: "", age: ""},
  ]
}
  • l
    Yes but (as far as I know) you're going to have to do it yourself
  • l
    If you look at the actual body of the 
    json-enc
    extensions it's really small:
    Copy code
    js
htmx.defineExtension('json-enc', {
    onEvent: function (name, evt) {
        if (name === "htmx:configRequest") {
            evt.detail.headers['Content-Type'] = "application/json";
        }
    },
    
    encodeParameters : function(xhr, parameters, elt) {
        xhr.overrideMimeType('text/json');
        return (JSON.stringify(parameters));
    }
});
    Basically just listens for the event, changes the content type, and and runs the 
    JSON.stringify
    function. You could replace that line with a few lines that parse the number of the person, and build the object so that it's an array of similar properties. There's no reason you need to do that on the frontend though
  • e
    Thank you very much. Let me give it a try
  • r
    https://htmx.org/events/#htmx:configRequest is the way to transform message content. You can parse the parameters in the handler and construct them into object. Then you pass this object further in 
    parameters
    field and it will be serialized by the extension
  • p
    I looks like HTMX doesn't care about a 
    target="_blank"
    added programmatically on the front-end... Any way around this?
1...105410551056...1146Latest