- How do I install filament-carve in a Laravel Filament project?
- Require the package with Composer (jeffersongoncalves/filament-carve), then register the plugin in your Filament panel provider so its resources and pages appear in the panel navigation. After registration, publish the package assets, views and config so you can customize them. Note that this is a thin integration layer over the Carve markup engine, not a replacement for Carve itself, so the underlying rendering dependency still ships with the package.
- Which Laravel and Filament versions does filament-carve support?
- Exact compatibility across Laravel and PHP versions is not stated in the release notes, so check the package composer.json and the markup-carve/laravel-carve bridge before scheduling an upgrade. The Filament major version deserves particular attention because the editor and table components are the most version-sensitive part of any admin framework integration. Confirm both constraints against your app before bumping.
- How do I publish the Carve configuration, assets and views?
- Use the standard Laravel vendor:publish command with the tags the package registers, which exposes config/carve.php plus the assets and views for full control. When re-publishing after an upgrade, diff the new config file against your existing one rather than overwriting it blindly. Finish by running php artisan config:clear in every environment, including CI and any container image that caches config at build time.
- Why did my Carve class imports break after upgrading to 3.1.0?
- Version 3.1.0 renames the vendor namespace from JeffersonGoncalves\Carve\ to MarkupCarve\LaravelCarve\, so any direct reference to the old classes fails. Treat the release as breaking despite the minor version number, because both the namespace and the config schema change. Do a global rewrite of imports across app/, tests/ and any first-party packages before running your suite.
- What happened to the profiles key in config/carve.php?
- The profiles key was renamed to converters in 3.1.0, and there is no Composer-level warning when a cached or published config still uses the old key. The failure surfaces at runtime as missing-converter behaviour or exceptions rather than as an install error. Port every custom entry from profiles to converters preserving nesting and defaults, then clear and rebuild cached config everywhere.
- Should I use CarveEditor, CarveEntry and CarveColumn directly in my application code?
- These UI components bind Carve rendering into form, table and entry surfaces, and consuming them directly is a supported way to build Carve-powered admin screens. The trade-off is upgrade scope: referencing the classes in your own code multiplies the namespace rewrite you must do when the vendor namespace changes. If you only interact through the published config, the blast radius stays much smaller.
- What is the AsCarve cast and do I need to test it?
- AsCarve is a model attribute cast that handles Carve markup stored on your Eloquent models, which is how Carve content usually reaches Filament forms and tables. A source-handling fix was published for the cast, so verify it against your own cast usage instead of assuming it applies to you. If your models store Carve content in unusual columns or via accessors, add an explicit test case.
- Is it safe to depend on markup-carve/laravel-carve ^0.1.7 in production?
- That bridge is pre-1.0 semver, which means the caret constraint permits breaking changes as soon as a 0.2.0 release lands. Because it sits directly under the editor components, it is the most version-fragile dependency in the path. If you accept that risk, pin an exact version and assign someone to watch upstream releases rather than relying on automatic updates.
- How do I verify the filament-carve upgrade didn't leave the old package behind?
- Run composer why jeffersongoncalves/laravel-carve and confirm it returns empty, then grep your codebase for the old JeffersonGoncalves\Carve namespace and check there are no hits outside vendor/. This matters because dual-package presence lets two providers register overlapping bindings if the old wrapper remains transitively or in a stale lockfile. Finish with config:clear and a fresh test run on every environment.
- Which major version of filament-carve should my team stay on?
- Upstream has published backports to 1.x and 2.x, which implies three majors are being maintained concurrently and gives you real patching options. That also means your major-version choice should be an explicit, documented decision rather than drift after an incidental composer update. Whichever line you pick, verify compatibility with your Filament and Laravel versions before scheduling the 3.1.0 namespace and config changes.