eslamteleb1 / auth-tasks-sample

a sample for reuse

About Laravel

Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experience to be truly fulfilling. Laravel takes the pain out of development by easing common tasks used in many web projects, such as:

• Simple, fast routing engine.
• Powerful dependency injection container.
• Multiple back-ends for session and cache storage.
• Expressive, intuitive database ORM.
• Database agnostic schema migrations.
• Robust background job processing.
• Real-time event broadcasting.

Laravel is accessible, powerful, and provides tools required for large, robust applications.

Learning Laravel

Laravel has the most extensive and thorough documentation and video tutorial library of all modern web application frameworks, making it a breeze to get started with the framework.

If you don't feel like reading, Laracasts can help. Laracasts contains over 1500 video tutorials on a range of topics including Laravel, modern PHP, unit testing, and JavaScript. Boost your skills by digging into our comprehensive video library.

Laravel Sponsors

We would like to extend our thanks to the following sponsors for funding Laravel development. If you are interested in becoming a sponsor, please visit the Laravel Patreon page.

Premium Partners

• Vehikl
• Tighten Co.
• Kirschbaum Development Group
• 64 Robots
• Cubet Techno Labs
• Cyber-Duck
• Many
• Webdock, Fast VPS Hosting
• DevSquad
• Curotec
• OP.GG
• WebReinvent
• Lendio

Contributing

Thank you for considering contributing to the Laravel framework! The contribution guide can be found in the Laravel documentation.

Code of Conduct

In order to ensure that the Laravel community is welcoming to all, please review and abide by the Code of Conduct.

Security Vulnerabilities

If you discover a security vulnerability within Laravel, please send an e-mail to Taylor Otwell via [email protected]. All security vulnerabilities will be promptly addressed.

License

The Laravel framework is open-sourced software licensed under the MIT license.

auth-tasks-sample's Issues

Sweep: open a new branch , make an event listener

open a new branch , make the event listener in the listener folder instead of the web file
solve the issue why the event is not fired or not working

Checklist

• app/Listeners/QueryExecutedListener.php

• Create a new class QueryExecutedListener that extends the base EventListener class.
• Move the event listener code from the web file to this new file. This includes the logic for handling the QueryExecuted event.

• app/Providers/EventServiceProvider.php

• Add a new entry to the $listen array for the QueryExecuted event. The value should be an array containing the fully qualified class name of the new QueryExecutedListener.

• routes/web.php

• Remove the event listener code for the QueryExecuted event. This code has been moved to the new QueryExecutedListener file.
• Remove the use statement for the QueryExecuted event if it is no longer used in this file.

Checklist

• app/Listeners/QueryExecutedListener.php

• Create a new class QueryExecutedListener that extends the base EventListener class.
• Move the event listener code from the web file to this new file. This includes the logic for handling the QueryExecuted event.
• Ensure that the QueryExecutedListener class is correctly implementing the handle method. This method should contain the logic for handling the QueryExecuted event.
• Make sure to import the necessary classes at the top of the file. This includes the QueryExecuted event and any other classes used in the handle method.

• app/Providers/EventServiceProvider.php

• Add a new entry to the $listen array for the QueryExecuted event. The value should be an array containing the fully qualified class name of the new QueryExecutedListener.
• Verify that the new entry in the $listen array is correctly formatted. The key should be the fully qualified class name of the QueryExecuted event and the value should be an array containing the fully qualified class name of the QueryExecutedListener.
• Ensure that the EventServiceProvider is correctly registering the events in the boot method. If necessary, add additional logic to this method to register the QueryExecuted event.

• routes/web.php

• Remove the event listener code for the QueryExecuted event. This code has been moved to the new QueryExecutedListener file.
• Remove the use statement for the QueryExecuted event if it is no longer used in this file.
• After removing the event listener code for the QueryExecuted event, make sure to test the application to ensure that it is still functioning as expected. If the event listener code was interacting with any other code in the web file, you may need to refactor this code.