You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wouldn't it be better to have Workflows and Activities registered automatically/placed by artisan commands in the app/Temporal folder instead of the root? In bigger projects that's a good separation because you can instantly see it's Temporal-related, especially if you have Actions and other Laravel layers in the root.
Currently:
It could have been:
The text was updated successfully, but these errors were encountered:
Yes it makes sense to group Workflows and Activities under a Temporal namespace.
For autodiscovery we can simply add the new namespace but for the make commands we should check if the project is using the new or the old structure and generate the class in the right namespace
Hi @michael-rubel
I've added support for the Temporal root namespace in 0.6.9.
If you want to use it, you just need to move existing workflows and activities to App\Temporal\Workflows and App\Temporal\Activities namespaces
Hi @cappuc
Wouldn't it be better to have
Workflows
andActivities
registered automatically/placed by artisan commands in theapp/Temporal
folder instead of the root? In bigger projects that's a good separation because you can instantly see it's Temporal-related, especially if you haveActions
and other Laravel layers in the root.Currently:
It could have been:
The text was updated successfully, but these errors were encountered: