Filament Jalali Datetime Laravel Package

Technical Evaluation

Architecture fit: ariaieboy/filament-jalali-datetime is a Filament plugin that adds Jalali (Persian) date/time form fields and table columns. It fits Laravel applications already using Filament admin panels where users need Persian calendar input/display while the database remains Gregorian. The package is UI-layer focused, so it does not alter core persistence architecture.

Integration feasibility: Composer install and plugin registration are straightforward for teams familiar with Filament. Release 1.4.2 adds PHP 8.4 to composer.json, which is a compatibility signal rather than a feature change. Integration effort is low assuming the host application’s Filament major version is supported. The primary feasibility question is Filament version compatibility, not PHP 8.4 itself.

Technical risk: Low for this patch. The release only widens the PHP constraint; it does not introduce new APIs, deprecations, or breaking changes. Residual risk sits with transitive dependencies: Filament version, Jalali conversion library, and Laravel/PHP constraint alignment. Timezone and Gregorian-vs-Jalali storage conventions remain the main correctness risks.

Key questions:

• Which Filament major versions (v3/v4) are supported by this release?
• Does adding PHP 8.4 drop support for older PHP versions, or is the constraint widened?
• Which Jalali conversion library is used, and is it actively maintained?
• Are dates stored as Gregorian in the database and converted only at the UI boundary?
• Is timezone handling documented and tested around DST and Asia/Tehran offsets?
• What is the test coverage and CI matrix for PHP/Laravel/Filament combinations?

Integration Approach

Stack fit: Best suited to Laravel + Filament applications serving Persian-speaking users. It is not a general Laravel date library; it is a Filament UI plugin. Teams not using Filament should not adopt it.

Migration path: Add via Composer, register the plugin/service provider per package docs, then replace standard Filament DateTimePicker and date column usages with the Jalali equivalents. Existing records should remain Gregorian in storage; migration should be UI-only unless the application already stores localized date strings, which would require data remediation.

Compatibility: PHP 8.4 is now declared in composer.json. Confirm the application’s Laravel and Filament versions satisfy the package constraints. If the application is on Filament v4, verify explicit support before rollout. Because this is a patch release, compatibility risk is low for existing installs already on 1.4.x.

Sequencing:

1. Verify PHP, Laravel, and Filament version constraints in a non-production branch.
2. Install 1.4.2 and register the plugin.
3. Replace a limited set of date fields/columns in a staging environment.
4. Validate Gregorian storage, Jalali display, timezone conversion, validation rules, and filtering behavior.
5. Roll out incrementally by admin panel or module, with rollback to the previous package version if UI regressions appear.

Operational Impact

Maintenance: Low ongoing maintenance for the package itself, but teams must track Filament major releases. The 1.4.2 PHP 8.4 addition reduces PHP-runtime upgrade friction. The package appears community-maintained, so dependency updates should be reviewed rather than assumed.

Support: No commercial SLA implied. Support depends on GitHub issues and maintainer availability. Teams should document a fallback path: reverting to standard Filament date components with server-side conversion if the plugin becomes incompatible.

Scaling: Negligible runtime scaling impact. Conversion and formatting occur at the UI layer. The main scaling concern is operational consistency across many admin panels, not throughput.

Failure modes: Filament major-version incompatibility after upgrades; incorrect timezone conversion around DST or midnight boundaries; inconsistent storage if some fields save Jalali strings instead of Gregorian dates; PHP constraint conflicts in composer.json; and locale/validation gaps for Persian date input.

Ramp-up: Low for developers already proficient with Filament. Teams new to Jalali date handling should budget time for storage conventions, timezone rules, and QA with Persian-language users. Release 1.4.2 itself requires no feature training or user communication.