You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ ] Regression
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
Errors produced by angular ssr client code, for example error ApolloError: Network error: Http failure response for https://example.com/graphql: 504 Gateway Timeout or variable blahblah is undefined are logged to the node console. Setting logger in NestFactory to false does nothing.
Would be nice to disable logging of all errors that come from angular or allowing them to be passed on to a custom logger, ex: sentry, bugsnag, console.log, etc...
Expected behavior
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
I'm submitting a...
Current behavior
Errors produced by angular ssr client code, for example
error ApolloError: Network error: Http failure response for https://example.com/graphql: 504 Gateway Timeout
orvariable blahblah is undefined
are logged to the node console. Setting logger in NestFactory to false does nothing.Would be nice to disable logging of all errors that come from angular or allowing them to be passed on to a custom logger, ex: sentry, bugsnag, console.log, etc...
Expected behavior
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Environment
The text was updated successfully, but these errors were encountered: