Weave Code
String Mapper Bundle Laravel Package
msales/string-mapper-bundle
A Symfony bundle from Msales for mapping strings to objects or values, providing a configurable way to convert raw string data into typed structures. Useful for deserialization and transformation tasks in PHP applications.
msales/string-mapper-bundle adds a small string-to-value mapping layer to Symfony applications. It resolves objects, class names, or callables from string keys through the service container, so code that dispatches behavior by identifier — event names, content types, format strings — avoids scattered switch statements and hard-coded lookup tables.
- Mappings declared in bundle configuration or via service tags
- Lazy resolution through the Symfony DI container
- Default/fallback mappings plus clear exceptions for unknown keys
- Pluggable mapper interface for custom resolution strategies
- Cache-friendly, framework-native integration
Frequently asked questions about String Mapper Bundle
- What is msales/string-mapper-bundle used for?
- It is a PHP and Symfony bundle for mapping and transforming strings between formats using configurable rules. It is intended to convert identifiers, keys, and labels consistently across an application. It is not a Laravel package, and its value is tied to Symfony bundle conventions.
- Does msales/string-mapper-bundle work with Laravel?
- Not natively. It is a Symfony bundle built around Symfony's DI container, bundle registration, compiler passes, and configuration conventions. Laravel would need a custom service provider and wrapper around extracted core classes, or a complete reimplementation. The Symfony bundle layer should be considered non-portable.
- Can I install msales/string-mapper-bundle with Composer in a Laravel app?
- You can attempt a Composer install, but resolution against modern PHP 8.2 or 8.3 and Laravel 10 through 12 is likely to fail. The package has 2017-era constraints and old Symfony component expectations. Do not force installation with platform requirement ignores; run a disposable spike instead.
- Which Laravel versions are supported by msales/string-mapper-bundle?
- None are officially supported. The last release was March 2017, so it predates Laravel 10 through 12 and modern PHP versions. Treat any Laravel use as an internal integration effort rather than supported package compatibility.
- What PHP versions does msales/string-mapper-bundle require?
- The 2017 release strongly suggests PHP 5 or 7-era constraints and outdated Symfony component expectations. Exact constraints should be confirmed from composer.json in an isolated spike. It is unlikely to be compatible with PHP 8.2 or newer without changes.
- Is msales/string-mapper-bundle maintained?
- Effectively no. It has 1 star, 0 dependents, a low score, and no recent releases. If adopted, your team would own security patches, PHP upgrades, Composer conflict resolution, and behavioral fixes.
- Is msales/string-mapper-bundle safe for production in Laravel?
- Not recommended. The package is effectively abandoned and has no meaningful community validation or support. Production use would create high operational risk unless you fork and maintain the minimal core with tests and modernization.
- Can I use the string mapping logic without Symfony?
- Possibly, but it must be verified. A spike should confirm whether plain PHP mapper classes can be instantiated without Symfony kernels or container services. If not, integration requires forking and stripping Symfony-specific wiring.
- What are alternatives to msales/string-mapper-bundle for Laravel?
- Reimplement the required mapping rules as a small Laravel service or custom package behind an interface. For narrow normalization use cases, a few well-tested classes are often enough. If you need the original behavior, fork only the minimal core and add a Laravel service provider.
- How should I test or migrate from msales/string-mapper-bundle?
- Define the mapping contract and acceptance cases first, then run a time-boxed install and usage spike. If the core is usable, vendor or fork it, remove Symfony bundle classes, update namespaces, and add golden-case contract tests. Roll out behind a feature flag and document ownership.
Weaver
How can I help you explore Laravel packages today?