- How do I install mziraki/nova-persian-date-field in Laravel Nova?
- Install it with composer require mziraki/nova-persian-date-field, then add the field to a Nova Resource's fields() method like any other Nova field. Clear Nova's cached assets if the component does not appear after install. Because adoption is minimal, exercise it on a single resource in staging before rolling it out across your admin panel.
- Does this field support Nova 5, or only Nova 4?
- The December 2024 release is contemporaneous with Nova 4, which is Vue 2-based, and Nova 5 moved to Vue 3/Inertia, so field components do not port automatically. Do not assume Nova 5 support from the README. Check the composer.json constraint and verify the component in a Nova 5 sandbox if that is your target major.
- Does it store Jalali or Gregorian dates in the database?
- It is intended as a presentation-layer field: Jalali is display-only and the stored value of record should stay Gregorian/UTC. If a build ends up writing Jalali strings, sortable(), range filters, and indexes degrade to string comparisons. Write Gregorian storage into your spike's acceptance criteria rather than discovering it in QA.
- Which PHP, Laravel, and Nova versions does this package support?
- Verify the exact constraints in the package's composer.json instead of inferring them from the README. The overlap with your app's PHP, Laravel, and Nova versions should be checked explicitly. Pin the package and its transitive dependencies in composer.lock once validated.
- Does the Persian date field handle timezones and Iran's DST changes?
- This is unconfirmed without reading the source. Iran abolished DST in 2022, so historical offsets differ from current rules, and a missing timezone contract causes silent off-by-one-day errors near midnight that render plausibly. Confirm whether it honors APP_TIMEZONE and per-user preferences or hardcodes Tehran before shipping.
- Can I use sortable(), filterable(), and Nova validation with this field?
- Verify these in a short spike rather than assuming. Sorting is safe when it falls back to the underlying Gregorian column; if it sorts a Jalali string, ordering and range filters will be wrong. Check nullable values and Nova validation rules on the same pass.
- Which Jalali conversion library does it use — morilog/jalali or verta?
- Check whether the field implements Jalali math itself or delegates to a vetted library such as morilog/jalali, hekmatinasser/verta, or ICU's fa-IR@calendar=persian. A pinned transitive dependency is preferable to vendored conversion code you would have to audit and patch yourself. Calendar correctness at leap days and year boundaries depends on this answer.
- Do I need a Node build step, or are the Vue assets pre-compiled?
- The overview describes a pre-compiled Vue component registered through Nova's asset pipeline, which suggests dist assets ship with the package. Confirm whether dist/ is committed and reproducible from source, or whether you inherit a Node build step you must maintain. This matters if you plan to fork.
- What are the alternatives to this package for Persian dates in Laravel Nova?
- Alternatives include other Nova Jalali date fields, a custom field wrapping morilog/jalali or verta, or a plain Nova DateTime field with client-side conversion. Given this package's minimal adoption, weigh each option on maintenance and Nova major support. A thin in-house field is a reasonable fallback for a single admin surface.
- Is this package actively maintained and safe for production?
- Treat it as maintainer-owned: one maintainer, roughly 5 stars, zero dependents, and a last release in December 2024. That is not a production contract, so plan a time-boxed spike with a named exit criterion and budget for forking if a Nova upgrade breaks the component. A small, authenticated admin surface keeps the risk modest.