Skip to content

fix(frontend): remove the Execution Settings hover popover next to the Run button#5118

Open
chenlica wants to merge 1 commit into
apache:mainfrom
chenlica:fix/remove-execution-settings-popup
Open

fix(frontend): remove the Execution Settings hover popover next to the Run button#5118
chenlica wants to merge 1 commit into
apache:mainfrom
chenlica:fix/remove-execution-settings-popup

Conversation

@chenlica
Copy link
Copy Markdown
Contributor

What changes were proposed in this PR?

Remove the "Execution Settings" hover popover that appears next to the Run button in the workflow editor. The popover contained a custom-execution-name input and an email-notification toggle, but the same defaults work for ~all users and the hover trigger was felt to be unnecessary UX clutter.

  • Drop the nz-popover directives and the <ng-template #executionSettings> block from menu.component.html.
  • The runWorkflow() handler already falls back to "Untitled Execution" when currentExecutionName is empty, so behavior on click is unchanged.
  • currentExecutionName (still declared as an unused @Input) and the email-notification toggle config flag remain in place for now; cleaning them up can be a follow-up if there's interest.

Any related issues, documentation, discussions?

No linked issue — small UX cleanup.

How was this PR tested?

Verified locally by applying the same edit to a running ng serve dev server: the hot-reloaded bundle no longer contains the "Execution Settings" string, and the Run button still triggers runWorkflow() with the default "Untitled Execution" name on click.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Claude Opus 4.7)

The "Execution Settings" hover popover next to the Run button — with an
execution-name input and an email-notification toggle — was unnecessary
UX clutter. The runWorkflow() handler already falls back to "Untitled
Execution" when no explicit name is provided, so removing the popover
leaves the Run button's behavior unchanged.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot added fix frontend Changes related to the frontend GUI labels May 17, 2026
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.18%. Comparing base (bfa79a7) to head (413afde).

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #5118      +/-   ##
============================================
+ Coverage     43.17%   43.18%   +0.01%     
  Complexity     2208     2208              
============================================
  Files          1045     1045              
  Lines         40254    40244      -10     
  Branches       4250     4250              
============================================
  Hits          17378    17378              
+ Misses        21804    21794      -10     
  Partials       1072     1072              
Flag Coverage Δ *Carryforward flag
access-control-service 39.53% <ø> (ø) Carriedforward from bfa79a7
agent-service 33.72% <ø> (ø) Carriedforward from bfa79a7
amber 43.85% <ø> (ø) Carriedforward from bfa79a7
computing-unit-managing-service 0.00% <ø> (ø) Carriedforward from bfa79a7
config-service 0.00% <ø> (ø) Carriedforward from bfa79a7
file-service 32.18% <ø> (ø) Carriedforward from bfa79a7
frontend 34.07% <ø> (+0.02%) ⬆️
python 90.43% <ø> (ø) Carriedforward from bfa79a7
workflow-compiling-service 56.81% <ø> (ø) Carriedforward from bfa79a7

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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

Labels

fix frontend Changes related to the frontend GUI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants