DateTimePicker errors when data has value not matching minutes step about filament HOT 7 CLOSED

Hmm, formatting on Filament's side may confuse devs if they don't expect their stored data to be formatted after hydration.

The native browser input would probably give an unexpected result too (like #13123 (comment)).
I'm going to close this issue for now, but tagging @danharrin to see if he thinks we should reopen and implement a "fix" in Filament.

from filament.

Hey @RicLeP! We're sorry to hear that you've hit this issue. 💛

However, it looks like you forgot to fill in the reproduction repository URL. Can you edit your original post and then we'll look at your issue?

We need a public GitHub repository which contains a Laravel app with the minimal amount of Filament code to reproduce the problem. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private / confidential, since we want a link to a separate, isolated reproduction. That would allow us to download it and review your bug much easier, so it can be fixed quicker. Please make sure to include a database seeder with everything we need to set the app up quickly.

from filament.

Thank you for providing reproduction steps! Reopening the issue now.

from filament.

Repository added: https://github.com/RicLeP/filament-datetime-bug

from filament.

I'm not sure if this should be treated as a Filament bug, or you should manually format the state to conform to the configured step after hydrating the field.

from filament.

I wasn't sure either. The error messages the browser gives are very confusing for anyone wanting to debug it, they've nothing to do with the data having the wrong values to work.

For me I see the issue being when external data has been imported, you don't know if it's in the right format. Or saving now() if left empty.

I agree that it can be resolved when hydrating but with combination of different data sources and the misleading errors (due to browsers more than Filament I think) I can see people being caught out.

Should inputs with minitrStep set hydrate correctly by default?

from filament.

Related issue - Textarea with numeric() set in a wizard. The user can enter commas, but if the field is on a prior wizard step when saving is throws a An invalid form control is not focusable. error in the browser. This stops the data being saved but shows no error or feedback to the user, just a cryptic message in the console.

from filament.