Skip to content

Conversation

Jeehut
Copy link
Member

@Jeehut Jeehut commented Dec 30, 2024

Fixes #17.

Note that I found a much simpler solution than what was outlined in the issue, which would have required a lot more work on our end (writing a Mac app) and also on the users end (setting up everything). This solution is much more practical and can be picked up by developers much more quickly. It's also less intrusive.

@Jeehut Jeehut changed the title Wip/handle errors Provide human-readable error chain description & error grouping APIs Dec 30, 2024
@Jeehut Jeehut requested a review from n0rthk1n9 December 30, 2024 11:25
Base automatically changed from wip/nested-errors to main January 19, 2025 09:09
Copy link
Collaborator

@n0rthk1n9 n0rthk1n9 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not having the chance of errors is bothering me a lot in my own code, I like it! After changing the German error message example to an English one, you can merge this.

@Jeehut Jeehut merged commit 5c09ef4 into main Jan 19, 2025
1 check passed
@Jeehut Jeehut deleted the wip/handle-errors branch January 19, 2025 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ErrorKit: Easy way to determine an "Error Call Stack"

2 participants