- What is cube-agency/filament-json used for?
- It provides a ready-to-use JSON form field for Filament admin panels, with syntax-highlighted editing, validation, and simple configuration. Typical uses are settings, metadata, and API payloads where you would otherwise build a custom component. It runs inside a Laravel application that uses Filament, so it adds capability without a second UI paradigm.
- How do I install filament-json in a Laravel app?
- Install it with Composer using composer require cube-agency/filament-json, then register the field or plugin in your Filament panel provider. Check the repository README for the exact registration snippet for your Filament major, because v3 targets Filament 5. Confirm your panel version before installing, since the package resolves against specific Filament and Laravel constraints.
- Which Laravel and Filament versions does filament-json support?
- The v3.0.0 release note scopes the major to Filament 5 and Laravel 13. It is not stated whether v3 also allows Filament 4, so check composer.json constraints before planning an upgrade. If you are on Laravel 11/12 or Filament 3/4, expect to stay on an earlier package major.
- Does filament-json work with Filament 4 or only Filament 5?
- Based on the v3.0.0 release note, the new major is aimed at Filament 5 and Laravel 13, but exclusive versus dual support is not documented. That is a blocking question to answer from composer.json. Dual support makes this a low-urgency item; exclusive support makes it part of your Filament 5 migration.
- Is filament-json production-ready?
- It is a focused Filament field, so production risk is mostly version lockstep with Filament and Laravel rather than runtime complexity. However, this assessment had no test coverage, CI matrix, or download data, so validate it in a staging panel first. Pin a version and review the changelog before taking a new major.
- How does filament-json validate JSON input?
- Validation is advertised as part of the field, but the available overview does not detail rule names or configuration keys. For critical payloads, combine the field's validation with your own schema or rule checks. Check the README for the exact validation API before relying on it alone.
- Can I customise the JSON editor in filament-json?
- The package advertises syntax-highlighted editing and simple configuration, but the available overview does not list specific options. Look at the published config and field methods in the repository for editor settings. Treat exact config keys as unverified until you check the source for your installed version.
- What is the upgrade path from v2 to v3 of filament-json?
- v3.0.0 is a major release tied to Filament 5 and Laravel 13, but no upgrade guide or breaking-change list was available in this assessment. Read the changelog and diff to determine whether v3 is a cheap compatibility bump or a genuine redesign. Plan the framework upgrade first, because the package can follow that migration but cannot lead it.
- Is there a support policy for older filament-json versions?
- The v2.x support window is unknown: security patches only, bug fixes too, or end-of-life. That answer decides whether staying on v2 is a viable holding position or a dead end. Ask the maintainer or check the repository's release and support notes before pinning.
- What are alternatives to filament-json for editing JSON in Filament?
- Alternatives include building a custom Filament field around a code editor or wrapping a general JSON editor component as a Filament form field. filament-json's advantage is that it is ready-made and validated, with no custom component to maintain. Choose it when you are committed to Filament and want the field to track Filament majors.