Introduces `code.nochebuena.dev/einherjar/core` — the foundational implementation module of the Einherjar framework. Provides four sub-packages that together cover every service's baseline needs: lifecycle management, structured logging, typed errors, and struct validation. - launcher: Launcher interface — three-phase managed lifecycle (OnInit → BeforeStart hooks → OnStart → OS signal wait → OnStop in reverse). Accepts lifecycle.Component and logging.Logger from contracts. Prints an ASCII art banner at startup (EINHERJAR_BANNER=off to suppress). Banner includes core version via runtime/debug.ReadBuildInfo() and a loaded-module list for every registered component that implements observability.Identifiable. Config struct with EINHERJAR_COMPONENT_STOP_TIMEOUT env tag (caarlos0/env syntax, default 15s). - logz: Logger implementation backed by log/slog. Returns contracts/logging.Logger. Detects errs.CodedError and errs.ContextualError (from contracts/errs) to enrich log records automatically — replaces the private duck-typed bridge from micro-lib. Context helpers: WithRequestID, WithField, WithFields, GetRequestID. Config struct with EINHERJAR_LOG_LEVEL (default INFO) and EINHERJAR_LOG_JSON (default false) env tags (caarlos0/env syntax); programmatic-only fields StaticArgs and Writer carry no tags. - xerrors: Typed error codes with context enrichment. Complete gRPC canonical set (16 codes) plus HTTP 410 ErrGone. Adds ErrOutOfRange, ErrAborted, ErrDataLoss over micro-lib. One convenience constructor per code. *Err declares compile-time satisfaction of errs.CodedError and errs.ContextualError. - valid: Struct validation wrapping go-playground/validator/v10. Validator interface + MessageProvider interface with full built-in tag coverage (~150 tags) in both DefaultMessages (English) and SpanishMessages (Spanish). Backend fully hidden; returns *xerrors.Err with ErrInvalidInput or ErrInternal. FieldLevel interface abstracts the backend's field-level access for custom validators. WithCustomValidator registers custom validation tags at construction time; OverrideProvider chains a tag→handler map with a fallback MessageProvider for custom tag messages without re-implementing built-ins. Compliance test enforces CT-6 (at most one exported TypeSpec per file via AST) and verifies behavioural correctness of all four sub-packages, including custom validator registration and OverrideProvider composition. Compile-time var _ assertions prove interface satisfaction. docs: ADR-001 (core module composition), ADR-002 (logz contracts/errs adoption), ADR-003 (Config naming convention and caarlos0/env tag standard)
4.2 KiB
ADR-002: logz adopts contracts/errs instead of private duck typing
- Date: 2026-05-28
- Module:
code.nochebuena.dev/einherjar/core - Status: Accepted
Context
In micro-lib, logz enriches log records when the error passed to Logger.Error
carries a machine-readable code or structured fields. It detects this at runtime
using two private interfaces defined inside logz:
// inside logz — never exported
type errorWithCode interface {
ErrorCode() string
}
type errorWithContext interface {
ErrorContext() map[string]any
}
xerrors.Err implements both via its ErrorCode() and ErrorContext() methods.
logz detects this with errors.As — without importing xerrors. The decoupling
is preserved. But the contract is invisible: a developer who wants their custom error
type to receive log enrichment must read logz's internal source to discover what
methods are required.
This approach is acceptable in micro-lib (single team, single repository, total visibility). In a framework distributed to third-party authors, it is a maintenance trap.
Decision
core/logz imports contracts/errs and checks errs.CodedError and
errs.ContextualError instead of defining private duck-typed equivalents.
// core/logz/logger.go
var ec errs.CodedError
if errors.As(err, &ec) {
attrs = append(attrs, "error_code", ec.ErrorCode())
}
var ectx errs.ContextualError
if errors.As(err, &ectx) {
for k, v := range ectx.ErrorContext() {
attrs = append(attrs, k, v)
}
}
core/xerrors declares compile-time satisfaction:
// core/xerrors/err.go
var _ errs.CodedError = (*Err)(nil)
var _ errs.ContextualError = (*Err)(nil)
Why the contracts/errs Sub-package Exists
contracts is the only Einherjar module guaranteed to have zero dependencies.
If CodedError and ContextualError lived in core/xerrors, any module
implementing a custom error type would be forced to import core — pulling the
launcher, logger, and validator into its dependency graph. That defeats the
Separated Interface pattern.
contracts/errs is a zero-dependency home for these two 1-method interfaces.
Any module can implement them without taking on any Einherjar dependencies.
Clean Separation Preserved
logz still does not import xerrors. Both import contracts/errs. The
decoupling is maintained; the contract is now visible.
contracts/errs (zero deps)
↑ ↑
core/logz core/xerrors
(imports) (implements)
A third-party error type implements errs.CodedError by satisfying one interface
from contracts — a zero-dependency import. It receives full log enrichment
automatically, without any wiring code.
Alternatives Considered
Keep private duck typing. Rejected — invisible to third-party implementors. A framework that requires developers to read its internal source code to understand what their types must implement is hostile to the developers it serves.
Export the interfaces from core/logz. Rejected — would force custom error
types to import core, violating the Separated Interface pattern. An error type
should not need to know about logging infrastructure.
One combined RichError interface. Rejected — ISP. An error may carry a
machine-readable code without structured fields, or structured fields without a code.
Forcing both into one interface imposes unnecessary constraints on implementors.
Consequences
Easier: Third-party error types have a clear, discoverable interface to implement:
go doc code.nochebuena.dev/einherjar/contracts/errs. Compile-time verification
replaces runtime discovery. The framework's own *xerrors.Err is provably correct
at compile time.
Harder: logz now imports contracts, adding one dependency to its import
graph. This dependency is zero-cost in practice — contracts has no external
dependencies and will not change its interfaces without a major version bump.
New obligations: The errs.CodedError.ErrorCode() and
errs.ContextualError.ErrorContext() signatures are permanent from contracts v1.0.0.
Any implementor of these interfaces is guaranteed that the signatures will not change
without a major version bump on contracts.