Better exception handling

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start by reading the two linked pull-request discussions, then inspect the affected areas in the Java client where generic Exception is caught. The work is done when those catches use more specific exception types in the areas identified by the discussions; the issue does not name tests or files to run.

Written by the indexing model from the issue text.

Description

In certain areas (as per comments linked below) we are catching the generic Exception class where we should be more specific.

https://github.com/Flagsmith/flagsmith-java-client/pull/65#discussion_r885534864
https://github.com/Flagsmith/flagsmith-java-client/pull/65#discussion_r885536045

Dominant language
Java
Stars
28
Forks
22
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Flagsmith/flagsmith-java-client

All issues in Flagsmith/flagsmith-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.