Prevent concealed component check affecting input min/max behaviour?
I guess this is done to prevent the validation triggering on hidden inputs but there must be a better way of doing this than always adding it manually.
9 Replies
What's the actual issue you have with this approach?
@Dennis Koch I feel like it should be handled properly revealing the collapsed parent component instead of preventing the basic form validation min/max/required
But those your addition change that?
Yeah you can manually add them but it seems a little backwards to lose this client-side validation and no mention of it in the documentation.
Can you share a screenshot of what happens when you have a closed section and a validation error with
->extraInputAttributes(['min' => 1]),
?There's no client side validation because it's hidden.
So what is the difference between your solution and Filament's solution if there is still no client side validation?!
Sorry not explaining very well. When the section is not hidden you get the client-side validation
When the section is not hidden you get the client-side validationIsn't that the same as what happens with the Filament code?