Uh oh!
There was an error while loading. Please reload this page.
feat(node): Check for invalid url in node transport - #6623
Conversation
If the tunnel option will cause an error to be thrown, catch it, and re-throw with a better error message. FixesgetsentryGH-6381
lforst
left a comment
There was a problem hiding this comment.
Thank you very much for the PR! I left some comments on how we can integrate this change into the project so it aligns with our vision.
Could you let me know if you have the time to implement it? Otherwise, I will put it into our backlog.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
440f7ac to
b20f95aCompare- Use `console.warn` instead of `logger.warn` - Do not re-throw the error
b20f95a to
034fd7bComparelforst
commented
Jan 5, 2023
After looking at what you wrote here,
I realized that the logic best lives in the node transport. I moved it there and added some tests. Sorry to stomp on your work like that but thank you very much for doing the foundational work and figuring everything out!! |
lforst
commented
Jan 5, 2023
@Naddiseo Thank you for your contribution! |
Naddiseo
commented
Jan 5, 2023
No worries! I did think it belonged in node-transport, but saw that |
If the tunnel option will cause an error to be thrown, catch it, and give a warning.
FixesGH-6381
Before submitting a pull request, please take a look at our
Contributing guidelines and verify:
yarn lint) & (yarn test).