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.
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(core): Reorganize error hierarchy in
core
andworkflow
packages (no-changelog) #7820refactor(core): Reorganize error hierarchy in
core
andworkflow
packages (no-changelog) #7820Changes from 4 commits
7749b85
cb1e9f7
9bd387d
4901026
6d968af
af5cf48
ff574e1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Since
ExecutionBaseError
now extendsApplicationError
, these checks could be unified, and we can most likely remove theExecutionBaseError
import all together here.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.
Do you mean unifying like
if (level === 'warning' || severity === 'warning') return null;
?If so,
severity
is present inExecutionBaseError
but absent inApplicationError
, so we'd still need to check fororiginalException instanceof ExecutionBaseError
, meaning the check is moved but not unified. Might be best to clean this up once we do away withseverity
altogether?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.
We can do this in another PR.
This file was deleted.
This file was deleted.