Exceptions are swallowed when using withCompilation flag
See original GitHub issueHey, per title, when returnOkOnError=false && withCompilation=true
I would expect to fail with calling
AnalysisResult.compilationError
instead of proceeding with the compilation.
Any reason we would not want to fail fast in that scenario?
Happy to submit a PR in case you agree with this case.
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:6
Top Results From Across the Web
Swallowing exceptions flag to turn that off? #1910 - GitHub
Swallowing exceptions (and just logging and not monitoring it) is generally not a good practice since stuff gets unnnoticed.
Read more >"unhandled exceptions" a problem? - Ask TOM
My main problem with this approach is that it consists of "swallowing" exceptions and allows the host program to ignore the error (either...
Read more >Unhandled exception swallowed (except in debugger)
I'm maintaining a legacy C# Winform application, using .NET 4.0 framework. The application works fine, but occasionally due to bugs in the ...
Read more >Error and Transaction Handling in SQL Server Part Two
Note: With the exception of this section, the output for all examples in this ... BrownShoesDontMakeIt AS BEGIN TRY RAISERROR('This error is swallowed',...
Read more >Principles of Exception Handling | Struts Survival Guide
If you catch an exception, don't swallow it. Log an exception where you catch it, ... Principle 10 is about the use of...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the remind, added to next milestone for discussion.
This actually looks like a bug to me after taking a deep look, basically the logic here ignores
returnOkOnError
whenwithCompilation
is set to true. Current plan is to fix it rather than introducing a new flag.