Skip to content

Conversation

@RohanSreelesh
Copy link
Collaborator

@RohanSreelesh RohanSreelesh commented Feb 4, 2026

What is the purpose of this change?

Added descriptions for workflow logic nodes. The descriptions are similar to the ones in the docs

How was this change implemented?

High-level approach - what files/components changed and why?

Added field picture:
image

How was this change tested?

  • Manual testing: [describe scenarios]
  • Unit tests: [new/modified tests]
  • Integration tests: [if applicable]
  • Known limitations: [what wasn't tested]

Is there anything the reviewers should focus on/be aware of?

Special attention areas, potential risks, or open questions

@github-actions
Copy link

github-actions bot commented Feb 4, 2026

WhiteSource Policy Violation Summary

✅︎ No Blocking Whitesource Policy Violations found in solaceai/solace-agent-mesh-ui-pr-967!

@RohanSreelesh RohanSreelesh changed the title DATAGO-123604: add descriptions for workflow logic nodes fix(DATAGO-123604): add descriptions for workflow logic nodes Feb 5, 2026
@sonarqube-solacecloud
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Copy link
Collaborator

@lgh-solace lgh-solace left a comment

Choose a reason for hiding this comment

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

If you have time, you could update the tests to use canvas? Thanks!

)}

{/* Description (for logic nodes) */}
{(node.type === "map" || node.type === "switch" || node.type === "loop") && LOGIC_NODE_DESCRIPTIONS[node.type] && (
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not a big deal, but could reduce the number of checks, removing LOGIC_NODE_DESCRIPTIONS[node.type] or something from the condition since we know it's there?

workflowConfig: null,
agents: [],
},
play: async () => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

The pattern pre-exists in this file, but I think it would be slightly beneficial to use the canvas, like this:

    play: async ({ canvas }) => {
        // Verify node ID appears twice: once in title header, once in Node ID section
        const pollingLoopElements = canvas.getAllByText("polling_loop");

It just makes the tests slightly more efficient since they are pre-scoped to the story container (we do need screen for things like dialogs or toasts since they are outside the canvas).

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants