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
Describe the bug
Laravel 11 discover events and listeners by default looking to app/Listeners directory.
After installing Orchid events autodiscovery stop working.
To Reproduce
Steps to reproduce the behavior:
Create an empty Laravel 11 project;
Add Orchid to the project;
Create an example event with php artisan make:event PodcastProcessed;
Create an example listener with php artisan make:listener SendPodcastNotification --event=PodcastProcessed;
Run php artisan event:list: no SendPodcastNotification or PodcastProcessed reference
Expected behavior
Laravel 11 events auto discovery working as out of the box.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: N/A
Browser: N/A
Version: N/A
Smartphone (please complete the following information):
Device: N/A
OS: N/A
Browser N/A
Version N/A
Server (please complete the following information):
Platfrom Version: 14.23.0
Laravel Version: 11
PHP Version: 8.3
Database: N/A
Database Version: N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Describe the bug
Laravel 11 discover events and listeners by default looking to
app/Listeners
directory.After installing Orchid events autodiscovery stop working.
To Reproduce
Steps to reproduce the behavior:
php artisan make:event PodcastProcessed
;php artisan make:listener SendPodcastNotification --event=PodcastProcessed
;php artisan event:list
: noSendPodcastNotification
orPodcastProcessed
referenceExpected behavior
Laravel 11 events auto discovery working as out of the box.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Server (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: