Weave Code
Workflow Bundle Laravel Package
integrated/workflow-bundle
A workflow bundle for PHP applications that lets you define state machines, transitions, and guards in configuration, then move records through them with a clean API. Includes event hooks, validation, and audit-friendly history.
Integrated Workflow Bundle
Frequently asked questions about Workflow Bundle
- Is integrated/workflow-bundle compatible with Laravel?
- The package name and namespace follow Symfony Bundle conventions, not Laravel package conventions, so compatibility is not confirmed by the metadata. A Laravel-native package would normally ship a ServiceProvider and optional Facade; this one appears to require a Bundle class and DependencyInjection extension. Treat Laravel support as an open question and confirm the framework contract before committing to an integration path.
- How do I install integrated/workflow-bundle in a Laravel project?
- The package is hosted on Bitbucket rather than Packagist, so installation likely requires a VCS repository entry and credentials that work in clean CI. Do not assume composer require will resolve it without manual repository configuration. Verify access, authentication, and a reproducible install from a fresh environment before planning application work.
- Does integrated/workflow-bundle wrap symfony/workflow or is it a custom engine?
- The provided materials do not say whether the bundle wraps symfony/workflow or implements a bespoke workflow engine. If it wraps the Symfony component, places, transitions, guards, and marking stores are well documented upstream and the bundle is mostly configuration wiring. If it is custom, read the source and treat coupling risk as significantly higher.
- What persistence model does integrated/workflow-bundle use?
- The metadata does not specify whether workflow state is stored through Doctrine, Eloquent, raw PDO, or an in-memory marking store. Workflow engines often assume a particular ORM or entity manager, so a Doctrine-oriented design would need an Eloquent bridge in Laravel. Confirm the persistence contract and any schema or migration requirements before adoption.
- How do I define state machines, transitions, and guards in integrated/workflow-bundle?
- The overview says definitions are configuration-driven and include state machines, transitions, and guards, but it does not show the exact format. Ask whether definitions use YAML, PHP config, or another loader, and whether guards are service references or inline expressions. Validate the configuration schema against your application's workflow rules in a small spike.
- Can I add custom guards and transition event hooks?
- Event hooks and validation are listed as package features, and guards are part of the configuration model, but the extension points are not documented in the excerpt. In Laravel you will need to know how custom guards are registered and how transition listeners receive events. Confirm whether these integrate with Laravel's event dispatcher or require a Symfony-style adapter.
- Does integrated/workflow-bundle provide audit history for workflow transitions?
- The blurb mentions audit-friendly history, which suggests transition records can support auditing, but it does not describe the storage model, schema, or retention controls. Ask where history is written, whether it is transactional with the state change, and how long records are kept. Plan archival or retention rules before production use.
- Which Laravel and PHP versions support integrated/workflow-bundle?
- No supported Laravel or PHP version matrix is visible in the provided metadata, and the Bitbucket hosting gives no Packagist release signal. An unversioned private package can break on PHP or Laravel upgrades without changelog coverage. Check composer.json constraints, tags, and the release cadence before relying on it.
- How should I test workflow transitions and guards in CI?
- Start with unit tests around each transition and guard, including invalid transitions and validation failures, using the package's public API rather than internal classes. Add an integration test that runs against the same persistence layer you plan to use in production. Because installation may require Bitbucket credentials, verify that your CI pipeline can resolve the package from a clean environment.
- What are alternatives to integrated/workflow-bundle for Laravel?
- If you need a Laravel-native workflow package, evaluate options that ship a ServiceProvider and documented Eloquent integration rather than Symfony Bundle conventions. If the bundle wraps symfony/workflow, you could also use the upstream component directly behind your own WorkflowService abstraction. Compare maintenance signals, test coverage, and upgrade paths before choosing.
Weaver
How can I help you explore Laravel packages today?