* feat(go): make go fmt git-aware by default - By default, only check changed Go files (modified, staged, untracked) - Add --all flag to check all files (previous behaviour) - Reduces noise when running fmt on large codebases Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(build): minimal output by default, add missing i18n - Default output now shows single line: "Success Built N artifacts (dir)" - Add --verbose/-v flag to show full detailed output - Add all missing i18n translations for build commands - Errors still show failure reason in minimal mode Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: add root-level `core git` command - Create pkg/gitcmd with git workflow commands as root menu - Export command builders from pkg/dev (AddCommitCommand, etc.) - Commands available under both `core git` and `core dev` for compatibility - Git commands: health, commit, push, pull, work, sync, apply - GitHub orchestration stays in dev: issues, reviews, ci, impact Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(qa): add docblock coverage checking Implement docblock/docstring coverage analysis for Go code: - New `core qa docblock` command to check coverage - Shows compact file:line list when under threshold - Integrate with `core go qa` as a default check - Add --docblock-threshold flag (default 80%) The checker uses Go AST parsing to find exported symbols (functions, types, consts, vars) without documentation. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: address CodeRabbit review feedback - Fix doc comment: "status" → "health" in gitcmd package - Implement --check flag for `core go fmt` (exits non-zero if files need formatting) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * docs: add docstrings for 100% coverage Add documentation comments to all exported symbols: - pkg/build: ProjectType constants - pkg/cli: LogLevel, RenderStyle, TableStyle - pkg/framework: ServiceFor, MustServiceFor, Core.Core - pkg/git: GitError.Error, GitError.Unwrap - pkg/i18n: Handler Match/Handle methods - pkg/log: Level constants - pkg/mcp: Tool input/output types - pkg/php: Service constants, QA types, service methods - pkg/process: ServiceError.Error - pkg/repos: RepoType constants - pkg/setup: ChangeType, ChangeCategory constants - pkg/workspace: AddWorkspaceCommands Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: standardize line endings to LF Add .gitattributes to enforce LF line endings for all text files. Normalize all existing files to use Unix-style line endings. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: address CodeRabbit review feedback - cmd_format.go: validate --check/--fix mutual exclusivity, capture stderr - cmd_docblock.go: return error instead of os.Exit(1) for proper error handling Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: address CodeRabbit review feedback (round 2) - linuxkit.go: propagate state update errors, handle cmd.Wait() errors in waitForExit - mcp.go: guard against empty old_string in editDiff to prevent runaway edits - cmd_docblock.go: log parse errors instead of silently skipping Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
59 lines
2.1 KiB
Go
59 lines
2.1 KiB
Go
// Package core provides a standardized error handling mechanism for the Core library.
|
|
// It allows for wrapping errors with contextual information, making it easier to
|
|
// trace the origin of an error and provide meaningful feedback.
|
|
//
|
|
// The design of this package is influenced by the need for a simple, yet powerful
|
|
// way to handle errors that can occur in different layers of the application,
|
|
// from low-level file operations to high-level service interactions.
|
|
//
|
|
// The key features of this package are:
|
|
// - Error wrapping: The Op and an optional Msg field provide context about
|
|
// where and why an error occurred.
|
|
// - Stack traces: By wrapping errors, we can build a logical stack trace
|
|
// that is more informative than a raw stack trace.
|
|
// - Consistent error handling: Encourages a uniform approach to error
|
|
// handling across the entire codebase.
|
|
package core
|
|
|
|
import (
|
|
"fmt"
|
|
)
|
|
|
|
// Error represents a standardized error with operational context.
|
|
type Error struct {
|
|
// Op is the operation being performed, e.g., "config.Load".
|
|
Op string
|
|
// Msg is a human-readable message explaining the error.
|
|
Msg string
|
|
// Err is the underlying error that was wrapped.
|
|
Err error
|
|
}
|
|
|
|
// E is a helper function to create a new Error.
|
|
// This is the primary way to create errors that will be consumed by the system.
|
|
// For example:
|
|
//
|
|
// return e.E("config.Load", "failed to load config file", err)
|
|
//
|
|
// The 'op' parameter should be in the format of 'package.function' or 'service.method'.
|
|
// The 'msg' parameter should be a human-readable message that can be displayed to the user.
|
|
// The 'err' parameter is the underlying error that is being wrapped.
|
|
func E(op, msg string, err error) error {
|
|
if err == nil {
|
|
return &Error{Op: op, Msg: msg}
|
|
}
|
|
return &Error{Op: op, Msg: msg, Err: err}
|
|
}
|
|
|
|
// Error returns the string representation of the error.
|
|
func (e *Error) Error() string {
|
|
if e.Err != nil {
|
|
return fmt.Sprintf("%s: %s: %v", e.Op, e.Msg, e.Err)
|
|
}
|
|
return fmt.Sprintf("%s: %s", e.Op, e.Msg)
|
|
}
|
|
|
|
// Unwrap provides compatibility for Go's errors.Is and errors.As functions.
|
|
func (e *Error) Unwrap() error {
|
|
return e.Err
|
|
}
|