Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Some handlers don't log extractors errors correctly #375

Closed
Totodore opened this issue Sep 29, 2024 · 0 comments · Fixed by #380
Closed

Some handlers don't log extractors errors correctly #375

Totodore opened this issue Sep 29, 2024 · 0 comments · Fixed by #380
Assignees
@Totodore
Labels
C-Bug Something isn't working

Comments

@Totodore
Copy link
Owner

Describe the bug
E.G with an async data handler when calling the Data extractor with a bad deserialization value. It should log an ERROR log before discarding the handler call.

Expected behavior
There should always be error log for extractors errors.

Versions (please complete the following information):

  • Socketioxide version: 0.14.1
@Totodore Totodore added the C-Bug Something isn't working label Sep 29, 2024
@Totodore Totodore self-assigned this Sep 29, 2024
@Totodore Totodore mentioned this issue Oct 20, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Totodore Totodore

Labels
C-Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(socketio/handler): trace extractor errors Totodore/socketioxide
1 participant
@Totodore