Follow-up from PR #174 (GetConfig) review. ConfigStore.Current returns a plain errors.New("node: Current: no config persisted yet"), which both GetConfig and SetManagement map to codes.Internal. A caller cannot distinguish "node has no config yet" (a precondition/not-ready state) from a genuine internal error.
Scope: add an exported sentinel (e.g. node.ErrNoConfig) in internal/node/providers.go, and have GetConfig + SetManagement map it to codes.FailedPrecondition. Low impact (a running linked node always has a persisted config), so this is polish, not a blocker.
Follow-up from PR #174 (GetConfig) review.
ConfigStore.Currentreturns a plainerrors.New("node: Current: no config persisted yet"), which bothGetConfigandSetManagementmap tocodes.Internal. A caller cannot distinguish "node has no config yet" (a precondition/not-ready state) from a genuine internal error.Scope: add an exported sentinel (e.g.
node.ErrNoConfig) ininternal/node/providers.go, and haveGetConfig+SetManagementmap it tocodes.FailedPrecondition. Low impact (a running linked node always has a persisted config), so this is polish, not a blocker.