Weave Code
Step Bundle Laravel Package
idci/step-bundle
IDCI StepBundle is a Symfony bundle for modeling and running sequential steps in PHP applications. It helps structure multi-step processes such as wizards and workflows with reusable step definitions, navigation, and lifecycle hooks.
IDCI StepBundle is a Symfony bundle for modeling multi-step processes as reusable, service-driven workflows. Each step is defined and wired through the container, letting you compose linear or branching flows without scattering control logic across controllers.
- Steps declared as services with clean dependency injection
- Configurable transitions between steps
- Event-driven hooks for custom logic at each stage
- Extensible base classes for domain-specific flows
- Native Symfony integration and configuration
Frequently asked questions about Step Bundle
- Can I use idci/step-bundle in a Laravel application?
- No. idci/step-bundle is a Symfony bundle, not a Laravel package: it assumes Symfony kernel/bundle registration, a DI container with tagged services, and likely the EventDispatcher and Config components. There is no service provider, facade, or publishable config in the Laravel sense, so it will not install or boot cleanly in a Laravel app. For Laravel, replicate the step pattern natively with Pipeline or chained queued jobs.
- How do I install idci/step-bundle?
- Install it with Composer and register the bundle in your Symfony application's bundle list, then define your steps as tagged services and describe the workflow in bundle configuration. Before committing, check the declared php and symfony/* constraints on Packagist, because compatibility with current Symfony LTS releases is unconfirmed. There is no Laravel-style config publishing step, so everything is configured through Symfony's container and bundle config.
- How are steps defined and ordered in idci/step-bundle?
- Steps are registered as tagged services in the Symfony DI container, with bundle configuration describing the ordered chain and per-step configuration; the engine then resolves the dependency-aware sequence and executes it. Read the source for the exact tag name and configuration schema, since documentation and community examples are thin. In Laravel terms, think of it as a config-driven pipeline definition rather than a facade-based API.
- Which Symfony and PHP versions does idci/step-bundle support?
- This is unconfirmed and must be verified first: inspect composer.json for the php and symfony/* constraints and check whether CI runs against a currently supported Symfony LTS. The recorded last release date is inconsistent with the present, so treat release cadence and recency as unverified and confirm tags directly on Packagist and GitHub. If you need Symfony 6 or 7 support, confirm it before designing anything around the bundle.
- How do I hook into step lifecycle events with idci/step-bundle?
- The bundle integrates with Symfony's EventDispatcher to expose lifecycle events around step execution, so you attach a listener or subscriber to add logging, metrics, notifications, or other side effects. The exact event class names and payloads should be read from source, since the README does not enumerate them. Laravel developers can map this concept to pipeline closures, model events, and job middleware.
- Does idci/step-bundle support branching, retries, and failure compensation?
- The overview describes an ordered, dependency-aware chain of steps, which suggests a linear-to-moderately-branching model rather than a full BPM engine. Conditional branching, automatic retries, and compensating actions on failure are not documented, so assume linear-only until you verify against the step contract in source. If your workflow needs rollback semantics, plan to implement them yourself around the engine.
- Can a workflow built with idci/step-bundle be persisted and resumed?
- There is no documented persistence or resume layer; execution appears to run in memory for the duration of the engine invocation. That makes it a poor fit for long-running imports where you need to checkpoint progress and restart mid-workflow. If you need resumability in Laravel, persist step state in the database and drive execution with idempotent queued jobs instead.
- How do I test a workflow built with idci/step-bundle?
- Unit-test each step service in isolation with mocked input and output, then integration-test the engine with a small fixture workflow defined in test configuration. Because the bundle has negligible adoption, there are no community test examples to copy, so budget time to build your own harness from source. In Laravel, the equivalent is faking the queue and asserting job chaining order.
- Is idci/step-bundle production-ready and actively maintained?
- Treat it as high risk: it is single-vendor maintenance by IDCI-Consulting with around 6 stars and 0 dependents, which is the profile most prone to silent abandonment. The MIT license makes it commercially safe to use and vendor, but there is no third-party battle testing or community support path. Pin the version, read the source rather than relying on docs, and keep the step contract behind an internal interface so you can swap in a homegrown runner later.
- What is the Laravel alternative to idci/step-bundle?
- Extract the bundle's step contract, namely input, output, next-step resolution, and configuration schema, into an internal spec and implement it with Laravel's Pipeline, queued jobs, and a steps config file. That gives you the same ordered, customisable, dependency-aware workflow with zero third-party risk and idiomatic observability. Use idci/step-bundle purely as a reference architecture if your stack is Laravel, not as a dependency.
Weaver
How can I help you explore Laravel packages today?