Weave Code
Lib Normalization Bundle Laravel Package
paysera/lib-normalization-bundle
A Symfony bundle that integrates Paysera’s normalization library, providing configurable normalizers and denormalizers for converting PHP objects to arrays and back—ideal for consistent API request and response data handling.
paysera/lib-normalization-bundle integrates the Paysera normalization library into Symfony, registering its normalizers as autowirable container services for cleaning and standardizing user input. It centralizes common data-hygiene tasks—stripping diacritics, folding Unicode characters, and normalizing free-text values—behind a framework-native API configured through standard bundle configuration.
- Registers normalizers through the Symfony DI container
- Handles diacritic removal and Unicode folding
- Configurable via standard Symfony bundle configuration
- Compatible with autowiring and service decoration
- Lightweight, with minimal setup required
Frequently asked questions about Lib Normalization Bundle
- What does paysera/lib-normalization-bundle do?
- It is a Symfony bundle from Paysera that bundles normalization utilities for cleaning and standardizing user-provided data such as names, addresses, and similar input. The goal is consistent, predictable values before you store or validate them. It ships as a Symfony bundle rather than a Laravel package, so the integration surface is Symfony's service container and DI configuration.
- Can I use paysera/lib-normalization-bundle in a Laravel application?
- Only indirectly. Laravel pulls in many Symfony components, but it does not run the Symfony framework or its bundle system, so the bundle's service wiring will not auto-register inside Laravel. Laravel teams typically port the underlying normalizer classes into their own service providers or call them directly rather than installing the bundle as-is. Verify the transitive Symfony version constraints in Composer before assuming a drop-in fit.
- How do I install paysera/lib-normalization-bundle?
- Install it with Composer, for example composer require paysera/lib-normalization-bundle, and confirm the resolved version is 1.4.0 or later if you need Symfony 7.4 support. In a Symfony application you then register the bundle in your kernel or bundles config. In Laravel, expect to wire the normalizers manually rather than relying on bundle auto-discovery.
- Does version 1.4.0 support Symfony 7.4, and which PHP and Laravel versions are supported?
- Release 1.4.0 is a compatibility-maintenance update that adds Symfony 7.4 support, with no new product capability announced. The release notes do not state an explicit Laravel or PHP support matrix, so check the package's composer.json constraints and README for the definitive answer. Laravel itself is not a declared target, so validate against your specific Laravel and PHP versions in CI rather than assuming coverage.
- Does Symfony 7.4 support in 1.4.0 raise the minimum dependency constraints?
- The release is described as additive compatibility work with no breaking changes or deprecations stated. That suggests existing lower Symfony constraints may still be allowed, but the only reliable answer is the composer.json in the tagged release. Run composer why-not paysera/lib-normalization-bundle 1.4.0 to see exactly what your project's current dependency graph would block.
- How do I configure and register the normalizers in my application?
- In Symfony, configuration happens through the bundle's service definitions and any extension config it exposes. In Laravel, register the normalizer classes as singletons or bindings in a service provider and inject them where you process input, such as form requests, imports, or model mutators. Consult the repository README for the concrete service IDs and options, since the excerpt provided here is empty.
- How should I test normalization behavior in my Laravel or Symfony test suite?
- Write unit tests that feed known messy input, such as inconsistent capitalization or spacing in names and addresses, and assert the exact normalized output. Add integration tests that exercise the normalizers through your actual container wiring so misconfiguration is caught. If you adopt 1.4.0, run your full suite against Symfony 7.4 in CI, since the release notes do not confirm an explicit test matrix.
- What is the risk of upgrading to 1.4.0 in production?
- Functional risk is low because the release is a compatibility update with no stated breaking changes. The realistic failure modes are Composer dependency conflicts, transitive Symfony constraint clashes, and untested runtime edge cases under Symfony 7.4. Adopt it on a branch, run dependency-resolution checks and your test suite, validate in staging, then promote.
- What are alternatives if I just need to normalize names and addresses in Laravel?
- Laravel's own validation and mutation features, such as form requests, custom rules, and model mutators, cover a lot of simple normalization without extra dependencies. Packages like propaganistas/laravel-phone or dedicated address-parsing libraries handle narrower problems better. Use this bundle when you specifically want Paysera's normalization rules and are comfortable consuming Symfony-oriented code.
- Is paysera/lib-normalization-bundle actively maintained, and is the release verifiable?
- The 1.4.0 release tracking Symfony 7.4 is a positive maintenance signal and reduces future upgrade friction for teams on newer Symfony component lines. There is no stated support policy or release cadence in the available context, so check the repository's commit history and tags directly. Confirm the 1.4.0 tag and its provenance on the tagged release before relying on it in production.
Weaver
How can I help you explore Laravel packages today?