Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate necessity of too large try-catch block #530

Open
Luro02 opened this issue May 13, 2024 · 0 comments
Open

Evaluate necessity of too large try-catch block #530

Luro02 opened this issue May 13, 2024 · 0 comments
Labels
question Further information is requested

Comments

@Luro02
Copy link
Collaborator

Luro02 commented May 13, 2024

Description

This is a good indicator for code that could be improved, but not worth subtracting points for.

The following questions arise:

  • What should be done instead? Having duplicate catch blocks? Doesn't always make sense to have different error messages and duplicate code is bad
  • As a workaround one could move the code in the try block into a method and then it is fine? Where is the logic?
@Luro02 Luro02 added the question Further information is requested label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant