Weave Code
Anzutap Bundle Laravel Package
anzusystems/anzutap-bundle
Anzu Systems Symfony bundle for TAP (Test Anything Protocol) test output. Integrates with PHPUnit so test results can be emitted in TAP format for compatible CI and reporting tools, with bundle configuration for Symfony projects.
At a glance
Frequently asked questions about Anzutap Bundle
- How do I install anzusystems/anzutap-bundle with Composer?
- Install it with composer require anzusystems/anzutap-bundle and let Composer resolve the current release. Because it ships as a Symfony bundle, you then register the bundle (or the corresponding service provider when bootstrapping it inside Laravel) so its services land in the container. After registration, add the bundle configuration for your Tap credentials and endpoints. Run the install in a staging environment first so you can verify autowiring and configuration before production.
- Does anzusystems/anzutap-bundle work in Laravel or is it Symfony only?
- The package is published as a Symfony bundle, not a native Laravel package, so there is no first-party facade or Laravel-specific config file documented. It can still be used from Laravel because Laravel's HTTP kernel and service container are built on Symfony components, and the bundle can be registered through service provider bootstrapping. Treat that integration path as supported but not officially documented, and confirm your Laravel version's underlying Symfony version matches the bundle's constraints.
- How do I configure Tap payment gateway credentials for the bundle?
- The bundle uses Symfony-native configuration to centralize Tap credentials, API endpoints, and environment settings. You supply your keys and endpoint values in the bundle config rather than scattering them through your domain code, which keeps payment flows decoupled and easy to swap between sandbox and live. Keep secret keys out of version control and load them from environment variables. Verify the exact configuration tree keys against the bundle's README, since the available options are defined by the bundle itself.
- Can I create a charge and check transaction status with this bundle?
- Yes. The bundle provides payment workflows for creating charges and for checking the status of an existing transaction, exposed as injectable services. You autowire those services into your own application services or controllers and map the resulting response objects into your domain model. This keeps Tap-specific request and response handling out of your business logic.
- How does the bundle handle Tap webhooks and payment callbacks?
- The bundle includes webhook and callback support so asynchronous payment updates can be received and mapped back into your application. You expose a route that forwards the incoming request to the bundle's handler, then act on the resulting status change. Because callbacks arrive from outside your application, validate the payload before trusting it and make the endpoint idempotent. The bundle handles the transport and response mapping; your application still owns whatever state transition the notification triggers.
- What changed in version 0.13.0 and should I upgrade from 0.12.0?
- Version 0.13.0 is described as a security-hardening release that escapes rendered attribute values and rejects script links. If your application renders package output that can include user-controlled attributes or URLs, treat this as a priority upgrade candidate rather than a routine bump. The release notes do not indicate breaking API changes, but the escaped output and rejected link schemes are behavior changes worth smoke-testing. Teams still pinned to 0.12.0 or earlier should evaluate 0.13.0 quickly.
- Will the 0.13.0 escaping and script-link rejection break my existing links or templates?
- It can, if your templates or downstream HTML consumers depend on exact output. Escaping applied to rendered attribute values may change the markup produced for dynamic attributes, and rejecting script links may block URL schemes that were previously accepted, such as javascript: links. Before rolling out, compare rendered output before and after the upgrade for anchors, relative URLs, mailto: links, and any user-generated content. The release notes do not document exactly which schemes are rejected or whether an option exists to intentionally preserve raw HTML, so confirm that behavior in your own environment.
- How do I test the AnzuTap bundle services in my application?
- The bundle exposes dependency-injection ready services that are designed to be autowired, which makes them straightforward to replace with test doubles in your container. Its HTTP layer is extensible, so you can substitute a custom client or a mock transport instead of calling the real Tap API during tests. Keep a small set of integration tests against Tap's sandbox for the charge and status flows, and unit tests for your own response mapping. If you render package output, add regression tests covering XSS payloads and script-link patterns after upgrading to 0.13.0.
- Which Symfony versions does anzusystems/anzutap-bundle support?
- The provided release information does not state Symfony version constraints, and version 0.13.0 does not mention Symfony version changes, deprecations, or new dependencies. Check the require block in the package's composer.json for the authoritative constraints before you commit. If you are running the bundle inside Laravel, cross-check those constraints against the Symfony version bundled with your Laravel release, since that compatibility question is independent of the 0.13.0 security fix.
- What are the alternatives to anzusystems/anzutap-bundle for Tap payments in PHP?
- You can call the Tap REST API directly with a PSR-18 or Laravel HTTP client, or use an official Tap SDK if one is available for PHP. The trade-off is that you then own credential handling, request retries, response mapping, and webhook processing yourself. The main reason to choose this bundle is that it centralizes Tap configuration, endpoints, and environment switching behind Symfony services that autowire cleanly. Weigh that convenience against the package's maintenance activity and its documented compatibility with your framework version.
Weaver
How can I help you explore Laravel packages today?