Implement error handling and improve resiliency for core and work #102
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request enhances error handling and testing for the
configureCoreTools
andconfigureWorkTools
functions. It introduces robust error management for API calls, ensures proper handling of null or empty results, and adds comprehensive test cases to validate these scenarios.Error Handling Enhancements:
Core Tools (
src/tools/core.ts
):try-catch
blocks to handle errors during API calls ingetTeams
andgetProjects
methods. Errors are now returned with descriptive messages, and null results are handled gracefully. [1] [2] [3] [4]Work Tools (
src/tools/work.ts
):try-catch
blocks for API calls ingetTeamIterations
,createOrUpdateClassificationNode
, andpostTeamIteration
. Added checks for null or empty API results and provided meaningful error messages. [1] [2] [3] [4] [5]Test Coverage Improvements:
Core Tools Tests (
test/src/tools/core.test.ts
):getProjects
andgetTeams
methods. Tests ensure proper behavior when API calls fail or return null results. [1] [2]Work Tools Tests (
test/src/tools/work.test.ts
):getTeamIterations
,createOrUpdateClassificationNode
, andpostTeamIteration
to validate error handling and null result scenarios. [1] [2] [3]GitHub issue number #57
Associated Risks
No risks
✅ PR Checklist
🧪 How did you test it?
Updated tests and re-ran before commit. Checked tools manually.