Skip to content

Develop #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 27, 2025
Merged

Develop #21

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0638ef3
Merge branch 'main' into develop
kpscyber Aug 27, 2025
acca3fe
Merge branch 'main' into develop
kpscyber Aug 27, 2025
c6b5300
Update readme
kpscyber Aug 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,8 +82,8 @@ This package doesnot provide user interface for user to manage workflow configur
## Usage
After you have completed setup, create workflow configuration in database using your own way or provided by other package. Then use them like the one you use by zerohadero/laravel-workflow. Storing configuration in database is easy to develop workflow for user.

## To Do
Curently guards should be created via event subscriber. I have a plan to use Symfony expression as upper guard layer. For example, you can write;
## Enhance your workflow
Using [zerodahero/laravel-workflow](https://github.com/zerodahero/laravel-workflow), guards should be created via event subscriber. I developed [soap/laravel-workflow-process](https://github.com/soap/laravel-workflow-process) to use Symfony expression as an upper guard layer. For example, you can write:

```
guard => $subject.isWaitingFor($user) || !$subject.isOwnedBy($user)
Expand Down