Skip to content

Add TriggerNode component with i18n support for graph view#64689

Open
windro-xdd wants to merge 1 commit intoapache:mainfrom
windro-xdd:fix-trigger-node-i18n
Open

Add TriggerNode component with i18n support for graph view#64689
windro-xdd wants to merge 1 commit intoapache:mainfrom
windro-xdd:fix-trigger-node-i18n

Conversation

@windro-xdd
Copy link
Copy Markdown

This PR adds a new TriggerNode component for rendering trigger nodes in the DAG graph view with proper internationalization support.

Changes

  • Add new TriggerNode.tsx component for rendering trigger nodes in the graph
  • Register TriggerNode in graphTypes.ts nodeTypes
  • Add graph.triggerDagRun translation key to all 21 locale files
  • Also add sensor node type registration for completeness

The TriggerNode component displays trigger nodes with:

  • A lightning bolt icon (FiZap)
  • The node label
  • An i18n-ready "Trigger DAG Run" subtitle text

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Opus 4.5 (OpenCode Agent)

Generated-by: Claude Opus 4.5 (OpenCode Agent) following the guidelines

- Add new TriggerNode.tsx component for rendering trigger nodes
- Register TriggerNode in graphTypes.ts nodeTypes
- Add 'triggerDagRun' translation key to all locale files (21 languages)
- Add 'sensor' node type registration for consistency
Copy link
Copy Markdown
Contributor

@bugraoz93 bugraoz93 left a comment

Choose a reason for hiding this comment

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

My review mainly excluding UI. For this specific content, I beleive we shouldn't need to translate

"taskCount_other": "{{count}} Görev",
"taskGroup": "Görev Grubu"
"taskGroup": "Görev Grubu",
"triggerDagRun": "TriggerDagRunOperator"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I am not sure we would need entry for unique Operator name. I don’t think so if they are all the same since no need to go into detail of translating each operator

@choo121600
Copy link
Copy Markdown
Member

choo121600 commented Apr 4, 2026

Could you share a screenshot of this part? It would help me better understand it.
Also, could you please revert changes to translation files other than English?
Each part will be handled separately by the respective translation contributors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants