Weave Code
Reform Laravel Package
ruwork/reform
ruwork/reform is a Laravel/PHP package for defining forms as reusable objects, mapping request data, validating input, and transforming it into typed values. It helps keep form handling organized, consistent, and testable.
ruwork/reform is a PHP package that turns form handling into dedicated, reusable form objects instead of scattered controller code. Each form declares its own fields, validation rules, and data mapping, so submitted input is processed consistently and can be tested in isolation.
Forms stay framework-agnostic while integrating cleanly with familiar validation workflows, making them suitable for both small CRUD screens and larger applications.
- Declarative field and rule definitions
- Typed access to submitted values
- Mapping form data to DTOs or entities
- Extensible fields and transformers
- Testable, dependency-free form classes
Frequently asked questions about Reform
- Is ruwork/reform a Laravel package?
- No. ruwork/reform is a Symfony-first form abstraction from Ruvents that layers typed form definitions over Symfony Form and Validator components. It ships no Laravel service provider, facade, config file, or Blade integration, so it is not a Laravel package in any practical sense.
- Does ruwork/reform work with Laravel 10 or 11?
- Not without hacks. Its last release pins PHP ^7.x and symfony/form ^3.4 or ^4.0, while Laravel 10 and 11 resolve Symfony 6 or 7 components, so Composer will report a hard conflict. The only routes are a fork, a replace hack, or --ignore-platform-reqs on an unsupported runtime, none of which is advisable for production.
- How do I install ruwork/reform with Composer?
- You would normally run composer require ruwork/reform, but on a modern Laravel or PHP 8.2 project that command will fail dependency resolution because of the legacy Symfony and PHP constraints. In an isolated legacy Symfony 4 environment it can install, but it is not recommended for new Laravel work. A fork with updated constraints is the realistic path if you want to evaluate the code.
- Which PHP and Symfony versions does ruwork/reform require?
- The published release from July 2018 targets PHP ^7.x and symfony/form ^3.4 or ^4.0, and it relies on Symfony's Form and Validator event and type system. That means it is tied to Symfony branches that are end-of-life and cannot receive security patches. It will not resolve cleanly against Symfony 6 or 7 components that current Laravel versions use.
- Is ruwork/reform still maintained?
- No. The last tagged release was on 2018-07-26, and there is no visible CI badge, coverage signal, or recent activity. The repository is described as a read-only subtree split of Ruwork Reform. There are zero stars and zero dependents, so there is no community or issue history to rely on.
- Is ruwork/reform safe to use in production?
- It carries medium-high security exposure because it pulls in end-of-life Symfony 3.4 or 4.x components with no patch path. Abandonment risk is high after six-plus years without a release, and the bus factor is effectively one organization. For a production Laravel application, the safer choice is a maintained Laravel-native form and DTO stack.
- What are good Laravel alternatives to ruwork/reform?
- Laravel's own FormRequest, Validator, and Eloquent casting cover most form validation and mapping needs. For typed form objects and DTO mapping, spatie/laravel-data, Livewire forms, and Laravel Folio are the mainstream options. Those packages are actively maintained, integrate with Laravel's container and validation pipeline, and avoid running a second validation mental model.
- Can I fork ruwork/reform for a Laravel project?
- Yes, legally: the package is MIT licensed, so forking is permitted. Practically, you would need to retarget PHP 8.2 and Symfony 6 or 7, add a service provider and facade, and build a test suite, which is roughly two to four engineer-weeks plus permanent ownership. A shorter option is to read the source for design ideas and rebuild the typed-form-object pattern on Laravel's Validator and a DTO layer.
- What is the license of ruwork/reform?
- ruwork/reform is released under the MIT license, which permits forking, modification, and commercial use with attribution. That makes code-level reuse legally straightforward. You should still check individual source files for copyright headers or attribution carve-outs before copying code into a monorepo.
- What does ruwork/reform's form DSL offer over Laravel validation?
- Reform's value is its typed form-object DSL: you define fields and mapping in PHP classes rather than arrays, which can feel cleaner than Laravel's rule arrays. However, that ergonomic gain comes with Symfony Form semantics, its event system, and a second validation model. Most Laravel teams get 80 percent of the benefit from FormRequest plus spatie/laravel-data without the foreign abstraction.
Weaver
How can I help you explore Laravel packages today?