[LiveComponent] min_length should no apply any constraint on 0 lenght

[kimu]

I understand this might be controversial.
But, when min_lenght modifier is applied to an input field

<input type="search" data-model="min_lenght(3)|query" />

As expected, the re-rendering won't fire until the value is 3 characters long. But, If one resets the field to 0 length, my expectation is that a re-render is fired to take the state of the page/component to the initial state.
Instead, nothing happens because min_lenght prevents that. That is particularly true if the "X" on the field of type search is not hidden.

If a user clicked on the "X", I think the expectation is to reset to the initial state, especially for a search field.

Would make more sense to apply the min_length constrain on anything above 0, or to give another parameter which allows to exclude 0 from it?

I haven't tried to see if using some workaround, like a live action or a onUpdated handler one can force the component to re-render if the value is changed to an empty string. I guess it can be done, but I wonder if this should not be a baked in the behaviour of the modifier itself.

All of the above, becomes even more complicated if this input field is a child component that is linked to the parent component through data-model props:props.

[xDeSwa]

If you can define an action for X

#[LiveAction]
public function resetInput(): void
{
    $this->query= "";
}

this way you can set up reset logic

[kimu]

@xDeSwa that is a not a custom button. That is the default clearing button that some browsers put in input fields of type search.
Something I usually hide through CSS.
I mentioned that just to illustrate how this behaviour with min_length plays againsts some of the default behaviours of some input fields.
I don't know if there is a specific event being fired when that button is clicked, but googling around it does not look like there is, so it would be very difficult to intercept that particular interaction from the user.
Being something you can hide is also not something that should be relied upon to mimick the desired behaviour.

The problem with the current behaviour of min_length is that it prevents to trigger the onUpdated handler that could be used to check the status of the field.
My rationale here is that the constraint should be applied when there is content in the field, thus when the field has at least 1 length.
Length 0 is no content, as such it should not apply the constraint. If the field has changed and the content is now empty it should trigger a re-rendering to restore the initial state or at least it should be possible to flag that option.

I can see that this behaviour could maybe cause issue with some other usage of it, so maybe another parameter, like skipWhenEmpty=true could be used instead.