-
Notifications
You must be signed in to change notification settings - Fork 230
docs: Added filtering technical information #2161
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.
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
Conversation
Edited "Broked.md" Edited "Decorator.md" Edited "Direct.md" Edited "Object.md"
Added "X mark" style Added "Checked mark" style Added "Warning mark" style
Redesigned pins & fixed conflicts
Redesigned pins & fixed conflicts
Redesigned pins & fixed conflicts
Redesigned pins & fixed conflicts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
@kumaranvpl can you please take a look and merge this one when u are free? |
One small, but very seriously conflict in publisher's (decorator, asyncapi support) page is fixed |
@Lancetnik I made extremely minor improvements - 1ce4af9. Pushed docs changes were good already. |
if await handler.filter(msg): | ||
return await handler.process(msg) | ||
|
||
raise HandlerNotFoundError |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I may be wrong, but it seems to me that if the message has not been filtered by any handler, then the exception does not occur.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No description provided.