feat(workflow-executor): add info logging around step execution#1514
Merged
Scra3 merged 4 commits intofeat/prd-214-setup-workflow-executor-packagefrom Mar 30, 2026
Merged
Conversation
1 new issue
|
Scra3
force-pushed
the
feat/workflow-executor-info-logging
branch
from
96c6af0 to
ef890a6
Compare
|
Coverage Impact Unable to calculate total coverage change because base branch coverage was not found. Modified Files with Diff Coverage (1)
🛟 Help
|
Add info level to Logger interface. Log step execution start (with context: runId, stepId, stepType, collection) and completion (with status) around doExecute in BaseStepExecutor. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ests Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…tdown - Remove duplicate info method in Logger interface and ConsoleLogger - Update console-logger test to match console.log implementation with level field - Add missing info mock in database-store tests Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
matthv
force-pushed
the
feat/workflow-executor-info-logging
branch
from
b30026e to
31cdb47
Compare
…eLogger console.log (info) vs console.error (error) already distinguishes the level via stdout/stderr. The JSON level field is redundant — users who need it can implement their own Logger. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Scra3
force-pushed
the
feat/workflow-executor-info-logging
branch
from
82effcb to
7802ae3
Compare
matthv
approved these changes
Mar 30, 2026
Scra3
merged commit df7e43a
into
feat/prd-214-setup-workflow-executor-package
30 checks passed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
infolevel toLoggerinterfaceBaseStepExecutor.execute()ConsoleLoggerwith structured JSON info logsinfoTest plan
🤖 Generated with Claude Code
Note
Add info-level logging to
BaseStepExecutor.executefor step start and completionAdds two info-level log statements in
BaseStepExecutor.execute: one at step start (loggingrunId,stepId,stepIndex,stepType, and base collection name) and one on successful completion (logging outcome status).Logger.infois also promoted from optional to required in theLoggerinterface, with all test mock loggers updated accordingly.Macroscope summarized 7802ae3.