refactor(errors): use specific error subclasses #344
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
YiweiShen
approved these changes
Jul 1, 2025
YiweiShen
deleted the
codez-chore-317-refactor-errors-use-specific-error-subclasses-3025450860
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #317
Applied changes based on Issue #317.
I’ve introduced concrete error subclasses and wired them into our core modules:
• New error types (
ConfigError,CliError,TimeoutError,ParseError,GitHubError) insrc/utils/errors.ts• config.ts now throws
ConfigErrorfor invalid/missing inputs• event.ts’s
loadEventPayloadthrowsParseErroron read/parse failures• client/codex.ts uses
CliErrorfor command failures andTimeoutErrorfor timeouts• api/openai.ts throws
ParseErrorwhen generated commit messages are invalid (to trigger fallback)• github/action.ts and github/github.ts now throw
GitHubErrorinstead of genericErrorfor GitHub‐related failuresThese changes give us much clearer error semantics without altering any existing test outcomes. Let me know if you’d like to extend this pattern to other areas or tweak any of the error types!