df-disable usage

[amikphoto]

I have a button in formcollection

edit_dish = Activator(
    label="Edit",
    required=False,
    widget=Button(
        action='activate(prefillPartial(DishSet.dish_form.dish_fk))',
        attrs={
            'df-disable': '!DishSet.dish_form.dish_fk',
            'df-hide': '!DishSet.dish_form.currentuser',
            'class': 'w-100 btn-outline-secondary',
        }
    ),
)

It should be disabled when DishSet.dish_form.dish_fk is not set. Everything works great when I set value in form or clear value of dish_fk field. But When I open formcollection It doesn't wotk. The button is still disabled but the value of dish_fk is setup.
Could you give me an advice where to go to solve this prooblem?

[amikphoto]

I've founded why 'df-disable': '!DishSet.dish_form.dish_fk' doen't work at start of the page. It's depending of filter_by attribute.
in my code: dish_fk = ModelChoiceField(queryset=DishLibraryModel.objects.all(),
widget=Selectize(
attrs={'hx-get': '/dishinfo','hx-target':'[name="dish_info"]', 'hx-swap': 'outerHTML',
'hx-trigger':'click from:.dish_trigger delay:100ms, load, change changed',
},
search_lookup='name__icontains',
filter_by={'cafe': 'cafe_fk__id'},
),
and if I delete filter_by it works. It seems to me its connected with incomplete status.

[jrief]

In order to reproduce this, I need more context.

[amikphoto]

Ок. I'll try to make it on testapp

[amikphoto]

so, I've made the example:

just added Reporter2 in EditIssueCollection

class IssueSingleForm(ModelForm):
title = CharField(
label="Title",
max_length=100,
)

reporter = ModelChoiceField(
    queryset=Reporter.objects.all(),
    label="Reporter",
    initial=Reporter.objects.get(pk=1),
    widget=Selectize(
        search_lookup='full_name__icontains',
    ),
    required=True,
)

reporter2 = ModelChoiceField(
    queryset=Reporter.objects.all(),
    label="Reporter2",
    initial=Reporter.objects.get(pk=1),
    widget=Selectize(
        search_lookup='full_name__icontains',
        filter_by={'reporter':'id'},
    ),
    required=True,
)


edit_reporter = Activator(
    label="Edit Reporter",
    widget=Button(
        action='activate(prefillPartial(issue.reporter))',
        attrs={'df-disable': '!issue.reporter2'},
        # button_variant=ButtonVariant.SUCCESS,
    ),
)
add_reporter = Activator(
    label="Add Reporter",
    widget=Button(
        action='activate',
        button_variant=ButtonVariant.PRIMARY,
        attrs={'df-disable': '!issue.reporter'},

    ),
)

class Meta:
    model = IssueModel
    fields = ['title','reporter']

IIn case I use filter_by={'reporter':'id'} condition doesn't work and the buttom stay disabled.

[jrief]

Thanks for reporting. I will replay this in my own setup and try to find out why this happens.

[jrief]

I just tried to reproduce your example. Something I do not understand is what filter_by={'reporter':'id'} should do? Model Reporter does not have a field reporter so what sould this filter do?

If you look at the "state" or "states" examples, there model County has a field state pointing on another model.

[amikphoto]

I used filter_by={'reporter':'id'} just to add filter_by in form In my real form I use real working filter. In this case I wanted to test the problem and this filter_by should just let set value to field reporter2.

This example is needed simply to show that when loading the page, the edit_reporter button with the attributes attrs={'df-disable': '!issue.reporter2'} is not active. Although it should be active.