refactor: Switch plain errors in nodes-base to ApplicationError (no-changelog) (#7914)

Ensure all errors in `nodes-base` are `ApplicationError` or children of
it and contain no variables in the message, to continue normalizing all
the backend errors we report to Sentry. Also, skip reporting to Sentry
errors from user input and from external APIs. In future we should
refine `ApplicationError` to more specific errors.

Follow-up to: [#7877](https://github.com/n8n-io/n8n/pull/7877)

- [x] Test workflows:
https://github.com/n8n-io/n8n/actions/runs/7084627970
- [x] e2e: https://github.com/n8n-io/n8n/actions/runs/7084936861

---------

Co-authored-by: Michael Kret <michael.k@radency.com>
This commit is contained in:
Iván Ovejero
2023-12-05 11:17:08 +01:00
committed by GitHub
parent 38b88b946b
commit e77fd5d286
33 changed files with 164 additions and 86 deletions

View File

@@ -1,5 +1,6 @@
import type { OptionsWithUri } from 'request';
import { ApplicationError } from 'n8n-workflow';
import type {
IDataObject,
IExecuteFunctions,
@@ -50,7 +51,10 @@ export async function venafiApiRequest(
errors = errors.map((e: IDataObject) => e.message);
// Try to return the error prettier
throw new Error(`Venafi error response [${error.statusCode}]: ${errors.join('|')}`);
throw new ApplicationError(
`Venafi error response [${error.statusCode}]: ${errors.join('|')}`,
{ level: 'warning' },
);
}
throw error;
}