So we saw in our previous article how to use the events in the database. Now we will see how to use the events in the request.
Request Events
Requests will have many events actually, let's see it.
-
validation
: Validation has also multiple events, let's see them:-
validation.validating
: This event is fired when the validation is started. -
validation.pass
: This event is fired when the validation is successful. -
validation.failed
: This event is fired when the validation is failed. -
validation.done
: This event is fired when the validation is done either successful or failed.
-
-
request
: Requests events list-
request.executingMiddleware
: This event is fired before executing all the middlewares. -
request.executedMiddleware
: This event is fired after executing all the middlewares. -
request.executingAction
: This event is fired before the action is executed. -
request.executedAction
: This event is fired after the action is executed and before the response is sent.
-
-
response
: Response events list-
response.sending
: Fired when the response is about to be sent. -
response.sent
: Fired when the response has been sent. -
response.success
: Fired when the response has been sent and the status code is2xx
. -
response.successCreate
: Fired when the response has been sent and the status code is201
. -
response.badRequest
: Fired when the response has been sent and the status code is400
. -
response.unauthorized
: Fired when the response has been sent and the status code is401
. -
response.throttled
: Fired when the response has been sent and the status code is429
, which means the request has been throttled. -
response.forbidden
: Fired when the response has been sent and the status code is403
. -
response.notFound
: Fired when the response has been sent and the status code is404
. -
response.serverError
: Fired when the response has been sent and the status code is500
. -
response.error
: Fired when the response has been sent and the status code is4xx
or5xx
.
-
Too Many Events? Yes, but it's very useful. Let's see how to use them.
So we have here mainly three types of events:
-
validation
: This series of events is by theValidator
class. -
request
: This series of events is by theRequest
class. -
response
: This series of events is by theResponse
class.
Each one of them has a different set of events, based on the situation of the event we'll start handle the event trigger.
🎨 Conclusion
We just introduced our Http Events types that will be used in our project, in our next article we'll start implementing first the validation
events.
🚀 Project Repository
You can find the latest updates of this project on Github
😍 Join our community
Join our community on Discord to get help and support (Node Js 2023 Channel).
🎞️ Video Course (Arabic Voice)
If you want to learn this course in video format, you can find it on Youtube, the course is in Arabic language.
💰 Bonus Content 💰
You may have a look at these articles, it will definitely boost your knowledge and productivity.
General Topics
- Event Driven Architecture: A Practical Guide in Javascript
- Best Practices For Case Styles: Camel, Pascal, Snake, and Kebab Case In Node And Javascript
- After 6 years of practicing MongoDB, Here are my thoughts on MongoDB vs MySQL
Packages & Libraries
- Collections: Your ultimate Javascript Arrays Manager
- Supportive Is: an elegant utility to check types of values in JavaScript
- Localization: An agnostic i18n package to manage localization in your project
React Js Packages
Courses (Articles)
Top comments (0)