Weave Code
Customer Bundle Laravel Package
softspring/customer-bundle
Softspring Customer Bundle is a PHP/Symfony package for modeling and managing customer accounts, profiles, addresses, and contact data. It offers reusable entities, services, and forms to speed up building customer management features in Symfony applications.
This bundle provides customer features.
Frequently asked questions about Customer Bundle
- Is softspring/customer-bundle compatible with Laravel?
- No. Despite appearing in PHP package catalogs, softspring/customer-bundle is a Symfony bundle: it registers through config/bundles.php, uses Symfony DI container compilation, Doctrine ORM entities, and Symfony Form types. There is no Laravel service provider, no Eloquent model, and no Laravel-native artifact of any kind. For a Laravel application the realistic use is as a design reference — read the customer, address, and contact model and reimplement it idiomatically with Eloquent models, migrations, policies, and Form Requests. Do not add it as a runtime dependency to a Laravel project.
- How do I install softspring/customer-bundle?
- Installation follows standard Symfony bundle conventions: require the package with Composer, register the bundle class in config/bundles.php, then configure the Doctrine mapping and any bundle options in your config directory. Because the package metadata is sparse, verify the available tags and the declared php and symfony/* constraints in its composer.json before requiring it. Run the install on a scratch branch or sandbox Symfony app first so a dependency conflict does not deadlock your locked project.
- What features does softspring/customer-bundle actually provide out of the box?
- Based on the package description, it ships Doctrine-backed customer entities with addresses and contact details, plus repositories and services for querying customers, and Symfony form types with validation for create and edit workflows. The stated design is integration-friendly for EasyAdmin and custom controllers. The published metadata does not document segmentation, groups, authentication integration, GDPR export or delete tooling, or B2B versus B2C distinctions, so treat the feature surface as unverified until you read the source.
- Which Symfony and PHP versions does softspring/customer-bundle support?
- This cannot be determined from the catalog metadata: there is no release matrix, no CI badge, and no documented support policy. You must read the composer.json constraints for php and symfony/* and check the date of the most recent tag. Then compare those constraints against your host application's lockfile to confirm a supported Symfony major. Assume compatibility is unproven until that check passes.
- Does softspring/customer-bundle use Doctrine or Eloquent for persistence?
- It uses Doctrine ORM. The bundle ships Doctrine-mapped entities for customers, addresses, and contacts, and its repositories are Doctrine repositories rather than Eloquent models. Doctrine mapping metadata does not interoperate with Eloquent, and there is no mechanical bridge between the two ORMs. If your application is Eloquent-based, plan to port the schema and relationships manually.
- Can I extend or override the customer entity in softspring/customer-bundle?
- The description states the structure is configurable and extendable following Symfony conventions, which typically means mapping overrides and Doctrine resolve_target_entities configuration. Whether the customer entity is genuinely overridable or hard-coded cannot be confirmed from the published metadata. Inspect the entity classes and the bundle's configuration tree before assuming you can swap in your own subclass. If the fields are hard-coded and unoverridable, adding application-specific attributes becomes invasive.
- Does softspring/customer-bundle integrate with EasyAdmin?
- The bundle is described as integration-friendly for EasyAdmin and custom controllers, and it belongs to the same Softspring ecosystem as sibling admin and CMS bundles, so that pairing is plausible. However, no admin controllers, CRUD controllers, or dashboard configuration are documented in the metadata. Expect to build your own EasyAdmin CRUD controllers over the provided entities and forms. Verify against your EasyAdmin major version, since its configuration API has changed significantly across releases.
- Is softspring/customer-bundle actively maintained and safe for production?
- The signals are weak: zero stars, zero dependents, a generic one-line description, and no visible CI or test suite, which is consistent with a dormant or incidentally published internal project. Assume there is no upstream fix path for bugs or security issues. This matters more than usual because a customer bundle stores names, addresses, contact details, and potentially credentials — PII and authentication-adjacent data. Read the code line by line, including validation and access checks, before it touches production data, and be prepared to fork and own it.
- What is a good Laravel alternative to softspring/customer-bundle?
- There is no Eloquent equivalent shipped in this package, so most Laravel teams build the domain first-party: customer, address, and contact models with migrations, relationships, factories, policies, and validation rules. That approach gives you full control over PII handling, GDPR export and deletion, and multi-address or B2B versus B2C variations. Use this bundle only as a reference for the schema shape and service boundaries, then implement the equivalent in idiomatic Laravel code. Evaluate any Laravel CRM or customer package separately against your own requirements.
- Will softspring/customer-bundle cause Composer dependency conflicts in my project?
- It can. Adding an unfamiliar constraint set, especially one pinning older php or symfony/* versions, to a locked application risks resolution deadlock. Use composer require with a dry-run or a throwaway branch, and run composer why-not to see exactly which constraint blocks resolution. For a Laravel host the conflict risk is largely moot because the framework mismatch makes the package unusable as a dependency anyway.
Weaver
How can I help you explore Laravel packages today?