Anyone have a good example of a way to swap form choices based on a previous form selection

isn't there on the docs?

I’ll have to see if it can be done with Django dorms

Forms

to change a field's queryset you just do something like

form.fields['field_name'].queryset = Model.objects.filter(...)

@green-activity-6102 the only issue I have is the field choices aren’t coming from a model but instead being returned from a api call

So I assume I can do what you stated above but after the equal sign slap the api call

same procedure but change

.choices

instead of

.queryset

note that choices is expecting a list of 2-tuples

Thanks I’ll give it a try in a little bit

Yeah I have a default choice field if the function fails to return correct data

So I need like [(“this is one”, 1), (“this is two”, 2)]

correct -- the field needs a human-readable value for display + the underlying value that is sent to the backend when the form is submitted

What htmx tag do I have to wrap around the first drop down

Also the Django form is type forms.Select

how you structure your HTMX really depends on how you want your application to function

I have limited use with htmx so what would you suggest. I have 8 fields on a form and one of them needs to trigger a different one to populate with respective choices the rest are static or keyboard input

Polling has been a great solution for me.

@green-activity-6102 when I do forms.field[‘fieldname’].choices = new choices and then return form[‘fieldname’] but it doesn’t update

polling is surprisingly effective. For a long time browsers implemented SSE as polling under the covers. Not sure what's happened since then.

Does anyone know how to access a value on a get from an Django form select and access the hx-include value

it's been a long time since I did this so I might be missing some details somewhere, I recommend reading the docs. Notably the docs also say you can pass a callable to the

choices

argument instead of a static list, that might be helpful for you https://docs.djangoproject.com/en/4.1/ref/forms/fields/#django.forms.ChoiceField.choices

should just be in your

request.GET

query dict

Thanks I got it now

Hey guys. Love to be a part of the community. I'm new here and also with HTMX + Django. 1. How do you structure your interactive partial URLs? Right now my strategy is to build the UI logic with Alpine and have a common form which is hidden and bind the values to that hidden form whenever something is changed and HTMX will take care of the partial rendering of results. Works smoothly for me but I wanted to know if there is a better way. 2. Is it a good idea to move the UI logic to the backend using HTMX by just keep swapping the UI elements if required?

Hi Waseem, welcome! I'm not a django developer, but here is my take on those two questions: 1). With my htmx apps I tend to structure the URLs around the UI needs of the application, beyond the first level. So, I'll have the standard

/contacts/

,

/contacts/34

, etc, but then I'll start getting things like

/contacts/34/details

for a details div that needs to poll or whatever. A bit different than how a JSON API would work. 2) In general, the more you can move to the backend, the better. If you have a lot of small changes that need to occur in the UI, then you probably want to expand the target of your HTTP requests to be as large as possible. If that won't work, there are other techniques available: https://htmx.org/examples/update-other-content/, but I always advocate keeping it as simple as possible

@mysterious-toddler-20573 That's a detailed answer. Thank you! 🙂

I've been using

django-compressor

for awhile to compress js and css...but now I'm wondering: is there really a point to compressing/minifying multiple already-minified files into a single file? or is it kind of diminishing returns at that point? I know this is kind of more Django than HTMX, but figured people here would have good insight

yeah fewer http requests