fix(eco): Report integration config errors to users when testing actions #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jasonyuezhang
force-pushed
the
gv/allow_integration_config_errors_to_flow_up
branch
from
2849a2a to
a337772
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a new exception type for reporting when showing users errors. These are distinct from form errors as they derive from configuration issues on the user side, but cannot be attributed to a specific field.
Updates ACI handling to consistently report exceptions in the same manner as our current rule actions.
\n\n---\nCopied from getsentry#100849\nOriginal PR: getsentry#100849