Dumbbell plot fails to initialize when “Show legends” appears selected but is not enabled

[kz930]

What happened?

The Show legends option in the Dumbbell Plot configuration is visually misleading.

The option appears blue, which makes it look like it is enabled by default. However, it is actually not selected. When I tried to run the Dumbbell Plot without manually clicking this option, the visualization failed to initialize.

Because the error message only said that the Dumbbell Plot could not be initialized, it was difficult to determine whether the problem was caused by the input data, the data format, or the legend configuration.

After manually clicking Show legends, the plot initialized successfully.

Expected behavior

The UI should clearly indicate whether Show legends is enabled or disabled.

Possible fixes include:

• Enable Show legends by default if it is visually shown as selected.
• Change the styling so that an unselected option does not appear active.
• Display a more specific validation message if this option is required.

How to reproduce?

1. Add a Dumbbell Plot operator to a workflow.
2. Connect it to valid input data in the required long format.
3. Open the Dumbbell Plot configuration panel.
4. Do not manually click the Show legends option, even though it appears blue or selected.
5. Observe that the Dumbbell Plot cannot be initialized because of Invalid Workflow.
6. Return to the configuration panel and manually click Show legends.
7. Run the workflow again.
8. Observe that the Dumbbell Plot initializes successfully.

Version/Branch

1.3.0-incubating-SNAPSHOT (main)

Commit Hash (Optional)

No response

What browsers are you seeing the problem on?

No response

Relevant log output

[github-actions]

👋 Thanks for your first contribution to Texera, @kz930!

If you're looking for a good place to start, browse issues labeled starter-task; they're scoped to be approachable for newcomers.

You can drive common housekeeping yourself by commenting one of these commands on its own line:

• Issues. Comment /take to assign an open issue to yourself, or /untake to release it. You can find unclaimed work with the search filter is:issue is:open no:assignee.
• Sub-issues. To link issues into a parent/child hierarchy, comment /sub-issue #5166 #5222 on the parent to attach those children (or /unsub-issue #5166 #5222 to detach them). From a child issue, comment /parent-issue #5166 to set its parent, or /unparent-issue to clear it (the current parent is detected automatically). References may be written as #5166 or as a bare 5166; cross-repository references are not supported.
• Pull requests (author only). Comment /request-review @user to request a review from someone, or /unrequest-review @user to withdraw that request.

Each command must match exactly: /take this will not work, only /take does. For the full contribution flow, see CONTRIBUTING.md.