- How do I install chengkangzai/filament-mui-date-picker in a Laravel Filament app?
- Installation follows the standard Filament plugin pattern: add the Composer package and run php artisan filament:assets. You should verify the package's composer.json constraints against your current Filament, Laravel, Livewire, and PHP versions before adoption. Make sure asset publication is part of every deploy, because the field depends on published front-end assets.
- Which Laravel, Filament, Livewire, and PHP versions does filament-mui-date-picker support?
- The provided release notes do not state supported Filament, Laravel, Livewire, or PHP version ranges. Check the package's composer.json and repository before adopting it, and test against your exact stack. Pin chengkangzai/filament-mui-date-picker to 3.1.1 and verify compatibility in a branch or staging environment.
- Is chengkangzai/filament-mui-date-picker compatible with Filament v4?
- Filament v4 compatibility is not confirmed in the provided release notes. The package is described as a Filament form-field plugin that layers a Material UI date picker over Filament's Livewire and Alpine form stack. Before using it with Filament v4, check composer.json and the repository, then pilot the field in a branch instead of assuming drop-in support.
- What bug was fixed in filament-mui-date-picker v3.1.1?
- v3.1.1 is a patch release that fixes a regression introduced in v3.1.0. In v3.1.0, a typed date could be discarded when the calendar was open, and dismissing the calendar could commit an empty value and wipe a saved value. v3.1.1 clarifies commit semantics so empty values are committed only via Clear, and it adds two tests, one of which fails on v3.1.0.
- Should I upgrade from filament-mui-date-picker v3.1.0 to v3.1.1?
- Yes, v3.1.1 should be treated as a recommended patch upgrade because it addresses a data-integrity regression. Teams on v3.1.0 should upgrade and then test typed dates with the calendar open, Escape dismiss, click-away dismiss, Clear, required and nullable validation, timezone edge cases, and keyboard-only entry. Deploy with the Filament asset step included and verify caching and CSP behavior in staging.
- How does filament-mui-date-picker handle empty, nullable, and required date fields?
- In v3.1.1, the commit semantics clarify that empty values are committed only via the Clear action, rather than by dismissing the calendar. This matters for nullable and required fields because a dismissed calendar should not wipe a saved or typed value. You should still exercise required and nullable validation paths across your forms and keep server-side validation as the source of truth.
- Does filament-mui-date-picker support localization, time zones, and daylight saving time?
- The package overview mentions customizable formats and localization, but the provided release notes do not detail timezone or daylight-saving handling. The TPM assessment explicitly raises timezone, localization, and daylight-saving boundaries as questions to verify between the client widget and server-side validation. Test edge cases in your target time zones before relying on the field for production date entry.
- What are the CSP and asset pipeline implications of using filament-mui-date-picker?
- The package introduces a non-Alpine front-end runtime and a separate JavaScript asset pipeline into the Filament admin surface. You need to determine whether the Material UI runtime is bundled locally or loaded from a CDN, and then review CSP and asset-size implications. Run php artisan filament:assets as part of deployment and confirm asset caching, CSP behavior, and Livewire navigation in staging.
- How should I test the Material UI date picker in Filament forms?
- Use a regression matrix that covers a typed date with the calendar open, Escape dismiss, click-away dismiss, the Clear button, required and nullable validation, timezone edge cases, and keyboard-only entry. Also test Livewire navigation between pages that contain the field and confirm asset caching and CSP behavior in staging. The release notes mention only two new tests and limited browser verification, with Chrome called out, so do not rely on package tests alone.
- Is chengkangzai/filament-mui-date-picker actively maintained, and what is the abandonment risk?
- The TPM assessment flags a single-maintainer bus factor and notes that the maintainer's support policy for the 3.1.x line is not stated. Browser verification is also described as limited, with release notes mentioning Chrome only. Pin 3.1.1, monitor the repository, and have a contingency plan in case the package is abandoned or stops tracking your Filament version.