Weave Code
Reform Bundle Laravel Package
ruwork/reform-bundle
A Symfony bundle that integrates Ruwork's Reform form library into your application, providing configuration and service wiring for building, validating, and processing forms with less boilerplate. It is aimed at projects already using Reform and Symfony's dependency injection and container conventi...
RuWork Reform Bundle integrates the Reform library into Symfony applications, providing a lightweight alternative for mapping request data onto typed objects. It wires the library’s core services into the container and exposes bundle configuration so forms can be defined and handled without boilerplate.
- Symfony bundle registration and service container integration
- Configurable form handling and request data mapping
- Autowiring-friendly service definitions
- Seamless fit with existing Symfony HTTP kernel workflows
- Minimal, dependency-light setup for typed form objects
Frequently asked questions about Reform Bundle
- Is ruwork/reform-bundle compatible with Laravel?
- No. ruwork/reform-bundle is a Symfony bundle from the Ruvent/Ruwork family; its Bundle class, DI extension, and compiler passes have no meaning in Laravel's service container. Bridging it would cost more than reimplementing the form concept natively in Laravel.
- Can I install ruwork/reform-bundle with Composer in a Laravel app?
- Composer may resolve it, but installing it in a Laravel app gives you nothing usable. There is no Laravel service provider, no facade, and no integration with Laravel's validation, CSRF, or request lifecycle. Treat any successful composer require as a false positive.
- What does ruwork/reform-bundle actually do?
- It integrates the Reform form library into Symfony applications by wiring Reform services into the Symfony service container. The goal is to define forms with less boilerplate and keep form configuration and processing cleaner. The practical value is unproven at zero adoption, so verify what it adds over Symfony Form before relying on it.
- Which Symfony and PHP versions does ruwork/reform-bundle support?
- The package was last released on 2018-07-09, which places it in the Symfony 3.x/4.x and PHP 7.x era. Its composer.json constraints may look permissive, but you must verify actual runtime compatibility with a spike rather than trusting metadata. Assume modern Symfony 6/7 and PHP 8.2+ are unsupported until proven otherwise.
- Is ruwork/reform-bundle still maintained?
- No. The repository is archived, the last release was 2018-07-09, and it has zero stars and zero dependents. There is no active maintainer, no CVE feed, and no downstream usage exercising it against modern frameworks. Treat it as source code to adopt, not an externally maintained dependency.
- Can I use ruwork/reform-bundle safely in production?
- Not without a fork, audit, and ownership. A form bundle sits directly on the request path, handling user input, CSRF tokens, and validation, and this one has no security review or maintainer behind it. PHP 7.x idioms may also break or emit deprecations on PHP 8.2+. Production use should only follow static analysis and a bounded compatibility spike.
- What are the best alternatives for forms in Laravel?
- For Laravel, use Laravel's native validation, FormRequest, Blade components, or an actively maintained package instead. For Symfony, compare against Symfony Form first, because the README-level value proposition of Reform is unproven at zero adoption. Reimplement the useful concept natively rather than pulling in an abandoned Symfony bundle.
- Can I fork and modernize ruwork/reform-bundle for PHP 8.2+ and Symfony 6/7?
- Yes, MIT licensing makes forking legal and cheap. The recommended path is spike, extract, wrap, and own: pull the useful classes into an internal package, drop the Bundle boilerplate and DI extension, rewrite wiring in modern Symfony config, and remove the upstream dependency from composer.json. Run PHPStan level 6+ and the Symfony deprecation detector before committing.
- Does ruwork/reform-bundle handle CSRF tokens and validation securely?
- It is part of the form handling layer, so it participates in CSRF and validation concerns, but there is no security review, CVE feed, or maintainer behind it. Because it has zero dependents, nobody is exercising it against modern Symfony, so failures will surface in your environment first. Do not assume secure defaults; audit input handling and token behavior yourself.
- How should I test whether ruwork/reform-bundle works with my Symfony version?
- Run a timeboxed spike in a throwaway Symfony app on your current framework version to see whether it boots and what it actually does. Check PHP 8.1+ deprecations, Symfony 5/6/7 form-event API changes, and reliance on abandoned polyfills. Confirm the business problem and whether an actively maintained alternative already solves it before extracting any code.
Weaver
How can I help you explore Laravel packages today?