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.

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

Add result to ObjectCommandResultError #341

Merged

Conversation

emilong
Copy link
Contributor

@emilong emilong commented Dec 21, 2023

When a ObjectCommandResultError is thrown, this change attaches the computed result to the error in case a custom error handler wants to use it for some reason.

In my case, I use Proxy objects to wrap Objects with a toString() property that I've been using since 2.9.0 but stopped working with the introduction of object checking and ObjectCommandResultError, but this change should allow me to deal with that in a custom error handler.

When a ObjectCommandResultError is thrown, this change attaches the
computed result to the error in case a custom error handler wants
to use it for some reason.
@emilong emilong marked this pull request as ready for review December 21, 2023 18:12
@jjhbw
Copy link
Collaborator

jjhbw commented Dec 28, 2023

Smart addition, thanks!

@jjhbw jjhbw merged commit c07c393 into guigrpa:master Dec 28, 2023
3 checks passed
@emilong emilong deleted the object-command-result-error-result branch December 28, 2023 18:40
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.

2 participants