-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat: Error handling #161
feat: Error handling #161
Conversation
k4lizen
commented
Dec 5, 2023
•
edited by aleksasiriski
Loading
edited by aleksasiriski
- Changed error messages to be more standardized
- Return errors in more places
- Made colly always run async to have easier error handling (async doesn't return OnError errors)
- Added comments after panics/fatals for clarity
- Pulled Request error handling from engines out to sedefaults
…ts, make every call async
golangci-lint run is a hard to remember command
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.
This is a huge PR, will need to do one more inspection before merging.
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.
Looks good, logic of when to fatal for db SET and GET can be done in a future PR.