Skip to content

fix: Node height #4424

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.

Sign up for GitHub

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

Merged
zhanweizhang7 merged 1 commit into from
Dec 3, 2025
Merged

fix: Node height #4424

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ui/src/workflow/common/data.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ export const knowledgeWriteNode = {
type: WorkflowType.KnowledgeWriteNode,
text: t('views.workflow.nodes.knowledgeWriteNode.text'),
label: t('views.workflow.nodes.knowledgeWriteNode.label'),
height: 252,
height: 100,
properties: {
stepName: t('views.workflow.nodes.knowledgeWriteNode.label'),
config: {
Copy link
Contributor Author

@shaohuzhang1 shaohuzhang1 Dec 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code you provided has two minor changes:

  1. The height property of the knowledgeWriteNode is reduced from 252 to 100 pixels.
  2. The value for the widthPropertyKey in the config section was changed to 'stepName'.

These changes may impact the visual layout of the workflow node on some interfaces. If these changes were intended, they align with reducing the size and focusing on the step name. However, without additional context about the specific requirements or constraints of your workflow application, it's difficult to determine whether either change is optimal.

If you have more details or if there are particular areas of concern (e.g., responsiveness, compatibility across different devices), feel free to share them so I can provide a more tailored response.

Expand Down
Loading