errors: use function for exit code
Metadata
Current evaluation
Merged a maintainer change to the error API that replaces a static exit code with a function. Approved by two reviewers with zero unresolved comments. The update modified three files (+3/-5 lines) and was integrated successfully.
Suggested action: —
No scores available.
Issue body
Just a quick change to the error API before it's actually used.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged a maintainer change to the error API that replaces a static exit code with a function. Approved by two reviewers with zero unresolved comments. The update modified three files (+3/-5 lines) and was integrated successfully. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a pull request updating the error API to use a function for exit code generation. The change was implemented ahead of the API's initial usage. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged a change to the error API that replaces the exit code with a function. This adjustment was applied before the API's implementation to streamline error handling. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #387 refactor: use exit code constants when possible | craft-application | merged | Merged refactoring that replaces hardcoded exit codes with constants. Approved by two reviewers and passed CI. Modifies four files and partially resolves issue #379. |