- How do I install the Filament Jalali DateTimePicker package in a Laravel app?
- Install it with Composer using composer require ariaieboy/filament-jalali-datetimepicker, then either register the plugin in your Filament panel provider or swap your existing DateTimePicker field for the package field class. On Filament v3 and Livewire 3 the happy path is short, because the integration is essentially a presentational swap over a datetime column. Pin the exact version you install, since the package is archived and will not receive compatibility fixes.
- Does this package support Filament v4?
- Assume it does not until you prove otherwise. The package is archived and has no path to Filament v4, whose DateTimePicker internals changed. Read composer.json to see which Filament and Livewire majors it constrains, and add a CI job that installs it against your pinned Filament version so a framework update cannot silently break date entry. If you need v4, plan to fork it or replace it with a maintained alternative.
- Does it store Jalali or Gregorian dates in the database?
- The intended contract is that the database keeps Gregorian values, ideally in UTC, while the field displays and accepts Jalali (Shamsi) input. The component converts on load and on save, so verify the round-trip yourself before trusting it. If it ever persists Jalali strings or local-time values, that is a hard-to-reverse data integrity problem, so add fixtures that assert exactly what lands in the column.
- How do I change the Jalali date format shown in the picker?
- The field exposes configurable display formats for the Jalali output rather than hard-coding a single Shamsi pattern. Check the README and the field class source for the exact format and configuration methods before wiring them into shared form schemas, since the package is archived and its docs may lag the code. Whatever format you choose, keep storage Gregorian so display preferences never leak into the database.
- Is an archived Composer package safe to use in production?
- It is safe only if you accept that maintenance becomes yours. There is no upstream security response, no bug fixes, and no path to Filament v4, and with 23 stars and a single maintainer there is little community pressure-testing of edge cases. The MIT license and small surface area make vendoring or a private fork practical, so treat it as a source dependency rather than a package dependency and isolate it behind your own field class.
- Does the Jalali picker handle Esfand 29 and 30 and Jalali leap years correctly?
- That is the domain hazard you must test rather than assume. Jalali leap-year rules, variable month lengths, Esfand 29 versus 30, midnight boundaries, and the 2022 abolition of DST in Asia/Tehran all produce off-by-one-day bugs that are silent and user-visible. Build round-trip fixtures around Nowruz, Esfand 29 and 30 in leap and non-leap years, year 1403, and Tehran offsets before you ship.
- Which picker modes does the Jalali DateTimePicker support: date only, time only, datetime, and ranges?
- Mode parity with Filament native DateTimePicker is an open question you should verify against the repo rather than the description. Check whether date-only, time-only, datetime, and range selection are all covered, and whether validation rules plus minDate and maxDate respect Jalali input. The underlying JavaScript datepicker also dictates RTL behavior, accessibility, CSP compatibility, and browser support.
- Does the package work for Filament table columns, filters, and inline-editable cells, or form fields only?
- The described scope is form fields, so do not assume table columns, filters, or inline-editable cells are covered. Audit each place you plan to display a Shamsi date and confirm the package ships a matching column or filter class before committing. Where it does not, keep the stock Filament component and convert with a Morilog or Verta layer instead.
- Can I show the Jalali picker only to Persian-locale users in a multi-tenant Laravel app?
- Yes, and you probably should. Fit is strong where the admin audience is Persian or Dari-speaking and weak everywhere else, so gate the Jalali field behind a locale check and keep the Gregorian DateTimePicker for other tenants. Wrapping the vendor class as App\Forms\JalaliDateTimePicker means only one file references the archived package, which is what you patch or fork at upgrade time.
- What are the alternatives to an archived Filament Jalali datepicker?
- Two viable routes exist: a maintained Filament Jalali plugin, or a generic datepicker combined with a Morilog or Verta conversion layer. Both avoid depending on an archived package, but a conversion layer moves the calendar-correctness burden into your own code, so the same Nowruz and Esfand fixtures are still required. Decide based on whether your pinned Filament version is supported and whether you would rather own a small component or a conversion helper.