- How do I install shalior/filament-persian-date-field in a Laravel Filament app?
- Install it with Composer by running composer require shalior/filament-persian-date-field. Laravel package discovery should register the service provider automatically, so no manual entry in the providers config is normally required. After that, reference the package's field class inside your Filament form schema. Run the install in a scratch branch first so you can confirm the constraints resolve against your exact Laravel, PHP, and Filament pins.
- Does filament-persian-date-field support Laravel 11 and Laravel 12?
- Version 2.0.1 declares compatibility with Laravel 11 and Laravel 12. That support is a Composer constraint declaration, not proof that a CI matrix exercises both versions, so verify it resolves against your exact laravel/framework pin using composer why-not. Laravel 11 and 12 also require PHP 8.2 or newer, so confirm your runtime matches before upgrading.
- What PHP version do I need for this Persian date field?
- Laravel 11 and 12 both require PHP 8.2 or newer, so plan on PHP 8.2, 8.3, or 8.4 for the package's stated supported range. The 2.0.1 release note does not spell out a PHP constraint, so read the require block in composer.json to be certain. If you are still on PHP 8.1 or lower, you are outside this package's supported Laravel versions anyway.
- Does the package convert Persian (Jalali) dates to Gregorian before saving to the database?
- The field is designed so users pick a Shamsi date and the package handles the conversion for form input, so you should not need to write manual conversion logic. What exactly gets stored depends on the field's configuration and your database column type, so check the form state value before persisting. Test a full round trip of create, edit, and save in staging to confirm the stored value matches what your domain expects.
- Is Laravel 10 still supported by shalior/filament-persian-date-field?
- It is not clear from the 2.0.1 release note whether Laravel 10 support was dropped or kept alongside 11 and 12. Diff the illuminate/support constraint between 2.0.0 and 2.0.1 before upgrading an app still on Laravel 10. If Laravel 10 support was removed, treat the version bump as a breaking change for your project rather than a routine patch.
- How do I use the Persian date picker inside a Filament form schema?
- Add the package's field class to your form schema the same way you would add a native Filament DatePicker, then set its label and validation rules. Because the input is Jalali-facing while your application likely persists Gregorian values, keep min, max, and required rules aligned with what actually gets stored. Check the README for the exact class namespace and the configuration methods the field exposes.
- Which Filament version does filament-persian-date-field work with?
- The package is a Filament form field, so the filament/filament version in your composer.json is the deciding factor. Check the package's require constraints against the Filament major version you run before installing. Composer will fail resolution loudly on a mismatch, which makes this a fast check rather than a runtime surprise. Pin both packages deliberately if you maintain multiple Filament projects.
- How do I test a Filament form that uses a Persian date field?
- Filament form fields can be tested with Livewire's testing helpers by mounting the component, filling the form state, and asserting the result. Because Jalali to Gregorian conversion sits between the user input and the database, assert on the persisted value, not only on the rendered field. Include a test with a known Shamsi date and its expected stored equivalent so any conversion regression fails loudly.
- What are the alternatives to shalior/filament-persian-date-field?
- Alternatives include building a custom Filament field around a JavaScript Jalali library such as jalali-moment or persian-date, or using a standard Filament date picker and doing the conversion manually in your form or model. This package exists to remove that custom glue for the common form-input case. Compare maintenance activity, Filament version constraints, and test coverage before picking an approach for a long-lived admin panel.
- Is shalior/filament-persian-date-field actively maintained?
- The only supplied signal is a patch release, 2.0.1, whose visible change is the Laravel 11 and 12 support declaration, and what changed in 2.0.0 is not documented in the notes. Before relying on it, review the repository's commit history, open issues, and whether CI actually runs against 11.x and 12.x. A one-line release note is weak evidence on its own, so validate the field with your own integration tests before shipping it.