Weave Code
Goaop Symfony Bundle Laravel Package
goaop/goaop-symfony-bundle
Go! AOP Symfony Bundle brings aspect-oriented programming to Symfony apps, letting you define aspects and advice to intercept service methods. It adds bundle configuration, AOP cache warming, and console tooling for weaving aspects into your code.
Symfony bundle for the Go! AOP framework: transparent aspect weaving for Symfony applications
Frequently asked questions about Goaop Symfony Bundle
- Can I use goaop/goaop-symfony-bundle in a Laravel application?
- No. This package is a Symfony bundle whose surface area is Symfony-specific: a Bundle subclass, a compiler pass for tagged aspects, kernel boot hooks, and a cache warmer tied to cache:warmup. None of that resolves in Laravel's container, and its Composer constraints are pinned to the Symfony 3.4/4.x era with the last release in February 2018. If you need AOP in Laravel, depend on goaop/framework directly and write a first-party Laravel bridge.
- How do I install goaop/goaop-symfony-bundle?
- For a legacy Symfony application, install it with Composer, register the bundle in your kernel, and configure aspects as tagged services. It cannot be installed as-is into a Laravel app because its dependency constraints target old Symfony versions. Verify PHP parser compatibility against your runtime first, since the package has had no releases in roughly seven years.
- What is goaop/goaop-symfony-bundle used for?
- It integrates the Go! AOP PHP framework into Symfony applications to enable aspect-oriented programming for cross-cutting concerns such as logging, caching, security, and transactions. Developers define aspects and pointcuts with annotations, and the bundle weaves them into service methods and classes automatically. It also adds configurable AOP caching, cache warming, and console tooling for production deployments.
- Does goaop/goaop-symfony-bundle support Laravel 10 or Laravel 11?
- No. It is a Symfony bundle with no Laravel service provider, no Artisan commands, and no Laravel container integration. Its last release was in February 2018 and its constraints are tied to Symfony 3.4/4.x, so it is not compatible with modern Laravel versions. Use Laravel middleware, events, observers, decorators, or ray/aop instead.
- What are the alternatives to goaop/goaop-symfony-bundle for Laravel?
- For AOP specifically, consider ray/aop or depending on goaop/framework directly with a custom Laravel bridge. For most cross-cutting concerns, Laravel's first-party primitives are safer: middleware, events and listeners, model observers, pipeline decorators, and explicit decorators bound in the container. Explicit decorators at container-binding time often deliver most of the value with far less risk.
- How does AOP weaving work in goaop/goaop-symfony-bundle?
- The underlying Go! AOP engine performs load-time source transformation by registering a stream wrapper that rewrites classes as they are autoloaded, generating proxied code into an aspect cache directory. The Symfony bundle adds configuration, an aspect container adapter, cache warming, and console tooling around that engine. In Laravel, classmap-authoritative or optimized autoloaders can bypass weaving, and opcache.preload and JIT bypass the stream wrapper entirely.
- Is goaop/goaop-symfony-bundle maintained and safe for production?
- It is explicitly labeled outdated, has zero dependents, no maintainer-backed CVE process, and no releases in roughly seven years, so it is unmaintained supply-chain surface. Technical risk is high because correctness depends on PHP parser compatibility with your exact runtime and on perfect cache invalidation across deploys. A PHP minor upgrade becomes a re-validation event rather than a routine bump.
- How do I configure aspects and the AOP cache in goaop/goaop-symfony-bundle?
- In Symfony you register aspects as services tagged for the bundle, let its compiler pass collect them, and rely on the cache warmer wired into cache:warmup. For production you should pre-warm and make the aspect cache authoritative at deploy time rather than weaving at request time. In a Laravel bridge you would replicate this with a ServiceProvider that registers the aspect kernel and an Artisan aop:weave command invoked in the deploy pipeline.
- Why are my aspects not being applied in Laravel with Go! AOP?
- Several cases fail silently: final classes, internal classes, closures, and code executed before your provider registers are not woven. Laravel's classmap-authoritative and optimize-autoloader modes can bypass the stream-wrapper interception path, and opcache.preload or JIT bypass it entirely. Also verify state handling because Go! AOP's AspectContainer is a process-global singleton, so per-request state inside an aspect can leak across requests in Octane or queue workers.
- Which Laravel features replace AOP use cases like logging, caching, and transactions?
- Laravel already addresses most AOP use cases with first-party primitives: middleware for request concerns, events and listeners for side effects, model observers for persistence hooks, pipeline decorators, and the decorator pattern at container-binding time. These approaches keep stack traces readable and avoid parser-level fragility. Only reach for AOP when a cross-cutting concern genuinely cannot be expressed with those tools.
Weaver
How can I help you explore Laravel packages today?