Weave Code
Coupon Bundle Laravel Package
elcodi/coupon-bundle
Coupon Bundle is part of the Elcodi e-commerce suite of Symfony components and bundles, providing coupon functionality for online stores. Note that this package is read-only; issues, questions, and pull requests belong in the main elcodi/elcodi repository.
[READ-ONLY] Subtree split of the Elcodi Coupon bundle
Frequently asked questions about Coupon Bundle
- Is elcodi/coupon-bundle a Laravel package?
- No. It is a Symfony bundle from the Elcodi e-commerce suite, not a Laravel package. There is no Laravel service provider, facade, config publishing, or Eloquent support. Dropping it into Laravel is a porting project, not a composer require.
- Can I use elcodi/coupon-bundle in a Laravel application?
- Not directly. It relies on Symfony's DI container, event dispatcher, Doctrine ORM mappings, and Elcodi Cart/Rule components. A Laravel integration would require a parallel Symfony stack, reimplementation with Eloquent, or extracting only value objects. The vendor does not support a Laravel path.
- How do I install elcodi/coupon-bundle?
- Install it with Composer in a Symfony application that matches its legacy constraints. Register the bundle in AppKernel or bundles.php and configure the required Doctrine mappings. Remember this is a read-only subtree split; issues and pull requests belong in the main elcodi/elcodi repository.
- Which Symfony and PHP versions does elcodi/coupon-bundle support?
- It targets the legacy Symfony 2.x/3.x era and PHP 5.6 through 7.x. PHP 8.x compatibility and modern Doctrine support are unverified and likely blockers. Check the upstream lockfile and test installation on your exact runtime before committing.
- Is elcodi/coupon-bundle maintained?
- The Elcodi suite has seen no meaningful activity for years. This split repository is read-only with zero stars and dependents, so community validation is minimal. Expect no security patches and treat it as an unmaintained dependency.
- What dependencies does elcodi/coupon-bundle require?
- Coupon logic is not standalone; it mutates cart pricing and likely depends on Elcodi CartBundle, RuleBundle, ProductBundle, Currency, Customer, and Doctrine. The full transitive dependency surface matters for integration feasibility. Inspect composer.json and the upstream monorepo before adopting it.
- Does elcodi/coupon-bundle handle concurrency and redemption idempotency?
- There is no evidence in the README-only maturity signal. Coupon engines must handle stacking rules, per-customer limits, partial redemption, race conditions, timezone-bound windows, and currency rounding. Ask upstream for tests covering concurrency and redemption idempotency.
- What are Laravel alternatives to elcodi/coupon-bundle for coupons?
- Implement coupons natively with Eloquent and Laravel events, or evaluate maintained Laravel promotion and coupon packages. Elcodi's coupon model can serve as a reference specification, but avoid carrying legacy Symfony baggage into Laravel. There is no supported Symfony-to-Laravel bridge for this bundle.
- Can I patch or fork elcodi/coupon-bundle?
- The repository is read-only and pull requests are redirected to the upstream monorepo. Any fix requires forking or vendoring, which erodes the value of taking a dependency. Assign clear ownership for a fork and plan for divergence from upstream.
- What should I check before adopting elcodi/coupon-bundle in production?
- First confirm the host application is Symfony and matches Elcodi's era. Then verify PHP and Doctrine compatibility, map your promotion model to Elcodi's rule vocabulary, review tests for concurrency and redemption, and assess security and fork fallback. In a Laravel application, re-scope this as a rewrite rather than an integration.
Weaver
How can I help you explore Laravel packages today?