Weave Code
Actions Laravel Package
laravilt/actions
Laravilt Actions is a lightweight Laravel package for encapsulating business logic in reusable, testable action classes. It helps keep controllers and models thin with dependency injection, validation, and clean composition for common workflows. Simple to adopt and easy to extend.
Complete form builder system with 30+ field types, validation, and Blade/Inertia.js integration for Laravilt. Build complex forms with text inputs, selects, date pickers, file uploads, rich editors, repeaters, and more.
Frequently asked questions about Actions
- What is laravilt/actions used for?
- Laravilt Actions is a form builder package for Laravilt, a Laravel admin panel system. It lets you define complex forms with more than 30 field types, including text inputs, selects, date pickers, file uploads, rich editors, and repeaters. It handles validation and renders forms through Blade or Inertia.js. Use it when you need structured, reusable admin forms without building every field and validation rule by hand.
- How do I install laravilt/actions in a Laravel application?
- Install it with Composer using composer require laravilt/actions. Laravel package auto-discovery should register the service provider, but check the package documentation for any required provider or facade registration. You should already have Laravilt installed and configured in your application. Publish any package configuration or assets if the installation guide instructs you to do so.
- Which Laravel and PHP versions does laravilt/actions support?
- The package targets Laravel applications that are compatible with the Laravilt admin panel, so your Laravel and PHP versions must satisfy Laravilt's own requirements. Check the composer.json constraints and the package README for the exact supported Laravel and PHP matrix before installing. Because Laravilt packages are versioned together, confirm that laravilt/actions matches your installed Laravilt panel version. If you are on an older Laravel release, verify compatibility in a staging environment first.
- How do I define form fields and validation with laravilt/actions?
- Forms are typically defined in PHP using the package's field classes, where each field declares its type, label, options, and validation rules. You compose fields into a form schema and let the package render the Blade or Inertia.js view. Validation rules follow Laravel's standard rule syntax, so existing Laravel validation knowledge applies. Keep form definitions in dedicated classes or methods so they stay reusable and testable.
- Does laravilt/actions work with both Blade and Inertia.js?
- Yes, the package is described as supporting Blade and Inertia.js integration for Laravilt. Blade rendering fits traditional Laravel admin panels, while Inertia.js support suits applications using a JavaScript-driven frontend. The right choice depends on how your Laravilt panel is set up. Confirm the required frontend dependencies and component setup in the package documentation.
- How do I handle file uploads and rich text editors in laravilt/actions?
- The package includes file upload and rich editor field types, so you configure storage disks, accepted file types, and size limits through the field definitions and Laravel filesystem configuration. For rich editors, review how HTML is sanitized and rendered in your frontend to avoid cross-site scripting risks. Test uploads with real file sizes and storage drivers such as local and S3. In production, ensure upload directories and disk permissions are correctly configured.
- How do I test forms built with laravilt/actions?
- Use Laravel's standard testing tools to assert that forms render expected fields and that validation rules reject or accept the right input. Feature tests can submit form data and check redirects, database changes, and validation error messages. Because the package builds on Laravel's validation layer, you can test rules independently of the rendering layer. Run these tests in CI against the same Laravel and PHP versions you use in production.
- What should I check before using laravilt/actions in production?
- Verify that file upload storage, validation rules, and rich text sanitization match your security requirements. Confirm that Laravilt panel authorization and policies are enforced for every form, action, and resource that uses the package. Check that published assets and configuration are deployed and cached correctly. Also test the full role matrix in staging, because form visibility and submit permissions may depend on Laravilt policies.
- What are alternatives to laravilt/actions for Laravel admin forms?
- Common alternatives include Filament's form builder, Laravel Nova fields, Livewire components with custom Blade views, and hand-built Blade forms with Laravel validation. Filament and Nova are full admin panel ecosystems, while laravilt/actions is specific to Laravilt. If you are already using Laravilt, staying within its package set usually gives the tightest integration. Evaluate alternatives based on field types, Inertia.js support, and long-term maintenance.
- How is laravilt/actions maintained and versioned?
- Laravilt packages follow semantic versioning, and patch releases are used for fixes while minor releases add features. Because Laravilt packages are often updated together, align laravilt/actions with the versions of laravilt/panel and related packages referenced in release notes. Read changelogs before upgrading, especially for authorization or validation changes. Pin versions in composer.json and upgrade in staging before rolling out to production.
Weaver
How can I help you explore Laravel packages today?