forms.ChoiceField with unicorn.

[bazubii]

I think I've had some issues working with forms.ChoiceField. Basically if you have something like this:

from django import forms
from django.db import models
from django_unicorn.components import UnicornView


class ExampleChoices(models.TextChoices):
    FIRST_CHOICE = "FIRST_CHOICE"
    SECOND_CHOICE = "SECOND_CHOICE"
    THIRD_CHOICE = "THIRD_CHOICE"


class ExampleForm(forms.Form):
    choice = forms.ChoiceField(choices=ExampleChoices.choices)
    dummy = forms.BooleanField()


class ExampleView(UnicornView):
    form_class = ExampleForm
    choice = ExampleChoices.FIRST_CHOICE.value
    dummy = False

    def example_choices(self):
        return ExampleChoices.choices

And a template something like this:

{% load unicorn %}
<div>
    <select unicorn:model="choice" id="choice">
        {% for choice in example_choices %}
            <option value="{{ choice.value }}">{{ choice.label }}</option>
        {% endfor %}
    </select>
    <input unicorn:model="dummy" type="dummy" id="dummy"> Dummy
</div>

What I see happening is that after you select a value (potentially having to click on dummy to get some round trips going) the forms.ChoiceField causes djanog_unicorn.components.unicorn_view.UnicornView.get_frontend_context_variables to use the django.forms.widgets.ChoiceWidget.format_value in a call like value = field.widget.format_value(cleaned_value) which forces this string into an array, "['FIRST_CHOICE"]" for example. I think I have a workaround to set the widget on the form field manually to something else other than the ChoiceWidget (maybe a TextInput or something else less custom than ChoiceWidget) and that seems to fix it. I don't know yet what I'd propose as a fix, but am I missing anything in this setup that I should be doing differently? I suppose all the widgets for form.Fields are not useful if we create a unicorn template without them.