Weave Code
Validation Bundle Laravel Package
sulu/validation-bundle
Validation bundle for Sulu CMS that brings Symfony Validator constraints to content types and forms. Define rules for content fields and form data to enforce data integrity, catch invalid input early, and keep your Sulu application's content reliable and consistent.
This bundle is for validation of schemas
Frequently asked questions about Validation Bundle
- Can I install sulu/validation-bundle in a Laravel application?
- Not realistically. It is a Symfony bundle that relies on Symfony bundle registration and DI container service definitions, and its last tagged release was April 2017 targeting PHP 5.6/7.0 and Symfony 2/3. Current Laravel requires PHP 8.1+ and ships Symfony 6/7 components, so Composer resolution will almost certainly fail before any code runs.
- What does sulu/validation-bundle do?
- It provides validation for Sulu CMS schemas by bringing Symfony Validator constraints to content types and forms. You define rules for content fields and form data to enforce data integrity, catch invalid input early, and keep Sulu content reliable and consistent.
- Is sulu/validation-bundle compatible with Laravel 10 or 11?
- No. It is a Symfony bundle, not a Laravel package, and it has no Laravel service provider or facade. Its PHP and Symfony version constraints are incompatible with modern Laravel, so you cannot install or bootstrap it in Laravel 10 or 11 without pinning legacy dependencies that block framework upgrades.
- What are the alternatives for schema validation in Laravel?
- Use Laravel's built-in Validator, Form Requests, and custom rule objects for conventional validation, and use maintained JSON Schema validators such as opis/json-schema or justinrainbow/json-schema for schema validation. Both options are actively maintained and fit Laravel's container and testing conventions far better than bridging a Symfony bundle.
- How do I configure validation rules for content fields in Sulu?
- In Sulu, you configure constraints through the bundle's Symfony service definitions and event subscribers that hook into Sulu's admin and content-schema lifecycle. That model does not translate to Laravel, where validation is configured through service providers, form requests, and rule classes.
- Is sulu/validation-bundle maintained?
- No. The repository is archived with zero stars and zero dependents, and the last tagged release was April 2017. There is no maintainer, no issue triage, no security patching, and no community knowledge base.
- Can I use sulu/validation-bundle in production?
- Not advisable in a Laravel application. Abandoned code that parses or validates user-supplied schemas is a latent attack surface you would own entirely, with no security patching or maintainer support. If you must evaluate it, isolate it in a throwaway branch or separate service, never in your main application's dependency graph.
- How do I test schema validation if I port rules from this bundle?
- Treat the bundle as a reference implementation: extract its validation rules and expected error semantics, then re-express them as Laravel rule objects or a dedicated SchemaValidator service. Build a fixture set from real schemas and assert that your error output matches the documented mapping.
- Does sulu/validation-bundle work with current Sulu schema formats?
- Unverified. There is no signal that the 2017 rule set matches current Sulu schema formats, so behavioral correctness is unknown. Confirm the exact schema version and expected error output before relying on its semantics.
- What is the migration path from sulu/validation-bundle to Laravel?
- Run a one-to-two-day spike to confirm the exact schema-validation requirement and expected error output, then evaluate maintained alternatives against a small fixture set of real schemas. Decide reimplement-versus-adopt and document the mapping from the old bundle's semantics. Build behind a SchemaValidator interface so the implementation is replaceable.
Weaver
How can I help you explore Laravel packages today?