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
Hey, thank you for this cool extension, I really like it. But I find it too intrusive to see these hints all around even if I cover all my code with error handlers. So, my suggestions:
Show hints to wrap function calls in try-catch blocks or adding .catch for async functions. When the user made it, remove these diagnostics.
Inside functions, if something throws and the function doesn't have @throws field in its jsdoc comment, show a warning on the function's name. When the user adds this field in jsdoc, remove warning diagnostics.
These changes may improve user experience, because instead of seeing intrusive hints they will focus on covering their code with error handlers.
The text was updated successfully, but these errors were encountered:
I just tried the extension, but immediately uninstalled due to lack of this:
Inside functions, if something throws and the function doesn't have @throws field in its jsdoc comment, show a warning on the function's name. When the user adds this field in jsdoc, remove warning diagnostics.
All I want is to ensure that all throws are documented.
Hey, thank you for this cool extension, I really like it. But I find it too intrusive to see these hints all around even if I cover all my code with error handlers. So, my suggestions:
Show hints to wrap function calls in try-catch blocks or adding .catch for async functions. When the user made it, remove these diagnostics.
Inside functions, if something throws and the function doesn't have
@throws
field in its jsdoc comment, show a warning on the function's name. When the user adds this field in jsdoc, remove warning diagnostics.These changes may improve user experience, because instead of seeing intrusive hints they will focus on covering their code with error handlers.
The text was updated successfully, but these errors were encountered: