-
Notifications
You must be signed in to change notification settings - Fork 32
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
refactor: Wrap a ton of stuff into try/catch and format #381
refactor: Wrap a ton of stuff into try/catch and format #381
Conversation
It was hard crashing the game otherwise.
Reviewer's Guide by SourceryThis pull request implements crash prevention and code formatting improvements. The changes involve wrapping code sections in try/catch blocks and applying the Gobo formatter. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
Hey @EttyKitty - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding error logging within the catch blocks to help diagnose issues in production
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
729f408
to
ce573be
Compare
@sourcery-ai review |
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.
Hey @EttyKitty - I've reviewed your changes - here's some feedback:
Overall Comments:
- While adding error handling is a good improvement, consider implementing more granular error handling for different failure cases rather than just wrapping everything in try/catch and destroying instances. Also consider adding proper error logging before destroying instances to aid debugging.
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
3984b88
to
ce573be
Compare
@sourcery-ai review |
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.
Hey @EttyKitty - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider handling specific exceptions instead of using blanket try/catch blocks to improve debugging and ensure only expected exceptions are caught.
- Ensure that exceptions are logged or handled appropriately in the catch blocks to aid in diagnosing issues.
- Consider adding automated tests to cover the critical paths wrapped in try/catch to ensure the changes don't introduce new bugs.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
pip.option3 = "Return your marines to the ship."; | ||
pip.image = "ancient_ruins"; | ||
} catch (_exception) { | ||
handle_exception(_exception); |
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.
handle_exception(_exception); | |
handle_exception(_exception); | |
instance_destroy(); |
Description of changes
Reasons for changes
Related links
How have you tested your changes?
Summary by Sourcery
Wrap critical code sections in try/catch blocks and apply consistent code formatting.
Bug Fixes:
Enhancements:
Summary by Sourcery
Wrap exception handling around code related to critical bug reports and format it using the Gobo formatter.
Bug Fixes:
Enhancements: