Download the PHP package maduser/argon-workflows without Composer
On this page you can find all versions of the php package maduser/argon-workflows. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download maduser/argon-workflows
More information about maduser/argon-workflows
Files in maduser/argon-workflows
Package argon-workflows
Short Description A PHP package for managing workflows
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package argon-workflows
Argon Workflows
A minimal workflow runner. Define state handlers and wire them together into workflows. Transitions can be static or triggered by signals emitted from handlers.
Basic Concept
Define a ContextInterface that represents the state of your system and passes through your workflow.
Each state has a StateHandlerInterface, which processes the context and returns a HandlerResult, possibly with transition signals.
The WorkflowRunner coordinates:
- Calling handlers in a loop
- Transitioning based on signal or static mapping
- Emitting execution events for logging, telemetry, queue correlation, or UI updates
The runner has a configurable max-step guard. This prevents broken workflow definitions from looping forever.
Example
Execution Events
The runner can emit execution events for run, step, and transition lifecycle changes.
Provide your own runId when you want to correlate runs with external systems.
Transition Behavior
If a handler emits a signal through HandlerResult::$signals, that takes precedence over the static transition.
If no signals match, the runner falls back to the static transition based on the current state.
Signal transitions are global in the current model:
- The first truthy matching signal wins.
- Signal transitions are not scoped to the current state.
- Use distinct signal names when the same signal would mean different targets in different states.
Graph Export
You can export a workflow definition as a graph to visualize it in a UI.
Signal transitions use from = '*' in the exported graph because they are global.
Integration Example
In a real project:
Interface Definitions
Implement:
ContextInterface: your workflow data object. The runner expectswithState()to return a context of the same concrete type.StateHandlerInterface: logic per step/state.
Boundaries
This package does not provide persistence, queue execution, scheduling, retries, locking, or dependency injection integration.
Observers fail the workflow if they throw. Wrap observers yourself if telemetry failures should be swallowed.
Handlers are registered directly in StateHandlerRegistry. Container-backed handler resolution belongs in an integration layer, not in the workflow runner core.
License
MIT License
