-
Notifications
You must be signed in to change notification settings - Fork 18.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(editor): Logs overview panel #14045
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is 📢 Thoughts on this report? Let us know! |
startedAt: Date | string; | ||
createdAt: Date | string; | ||
stoppedAt?: Date | string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing type to match the actual behavior (happens when the execution data is received from BE)
@@ -59,6 +59,7 @@ | |||
"core-js": "^3.40.0", | |||
"curlconverter": "^4.12.0", | |||
"dateformat": "^3.0.3", | |||
"element-plus": "2.4.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This library has been already in use. I'm adding it as an explicit dependency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Left a few minor comments
workflowId, | ||
data: parse(rawData), | ||
status, | ||
startedAt: workflowsStore.workflowExecutionData?.startedAt as Date, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we do a typeguard here instead of coercing it? Something like:
function ensureDate(value: string | Date | undefined): Date | undefined {
if (!value) return new Date();
if (value instanceof Date) return value;
return new Date(value);
}
} | ||
|
||
function handleClickToggleButton() { | ||
props.node.expanded = !props.node.expanded; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we emit an event here to not mutate the prop directly?
{ label: 'Details', value: 'details' }, | ||
{ label: 'Overview', value: 'overview' }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i18n 👁️
:icon="props.node.expanded ? 'chevron-down' : 'chevron-up'" | ||
:style="{ | ||
visibility: props.data.children.length === 0 ? 'hidden' : '', | ||
color: 'var(--color-text-base)', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we put this to toggleButton class? Also perhaps use v-show instead of visibility?
Summary
This PR implements the new design of logs overview panel behind feature flag.
To try out, set local storage key
N8N_LOGS_2025_SPRING
totrue
and refresh the browser.Note that the logs overview works only for workflows with AI agent node for now.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/SUG-23/feature-logs-overview-panel
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)