Skip to content

[One Workflow] Fix validation in Test Step modal by ensuring markers are set for all editors#251714

Merged
Kiryous merged 7 commits intoelastic:mainfrom
Kiryous:15680-fix-validation-test-step-modal-v2
Feb 6, 2026
Merged

[One Workflow] Fix validation in Test Step modal by ensuring markers are set for all editors#251714
Kiryous merged 7 commits intoelastic:mainfrom
Kiryous:15680-fix-validation-test-step-modal-v2

Conversation

@Kiryous
Copy link
Copy Markdown
Contributor

@Kiryous Kiryous commented Feb 4, 2026

Summary

Fixes validation in the Test Step modal's JSON editor by ensuring that monaco.editor.setModelMarkers is called for all Monaco editors, not just the main YAML editor.

Before

image

After

Screenshot 2026-02-04 at 21 15 54

Problem

The monkey patching of monaco.editor.setModelMarkers in workflow_yaml_editor.tsx was checking if the model URI matched the current editor's URI and skipping the marker setting call for non-matching editors. This prevented validation errors from being displayed in the Test Step modal's JSON editor.

Solution

The fix ensures that setModelMarkers is always called for all editors:

  • For the main YAML editor: markers are transformed and then set
  • For other editors (like Test Step modal): markers are set as-is without transformation

Changes

  1. workflow_yaml_editor.tsx: Added call to original setModelMarkers for non-matching editors before returning
  2. test_step_modal.tsx:
    • Fixed schema binding to use current model URI
    • Added data-test-subj for testing
    • Cleaned up commented code
  3. test_step_modal.stories.tsx: Added Storybook story for visual testing
  4. workflow_yaml_editor.test.tsx: Added unit test to verify monkey patching behavior

Testing

  • ✅ Unit test added to verify setModelMarkers is called for non-matching editors
  • ✅ Existing tests pass
  • ✅ Manual testing confirms validation now works in Test Step modal

Related Issue

Fixes: https://github.com/elastic/security-team/issues/15680

Kiryous and others added 2 commits February 4, 2026 20:14
… editors

The monkey patching of monaco.editor.setModelMarkers was skipping the actual
marker setting for non-main-editor models, which prevented validation errors
from appearing in the Test Step modal's JSON editor.

This fix ensures that setModelMarkers is called for all editors, while still
applying the custom marker transformation only to the main YAML editor.

Fixes: elastic/security-team#15680
Co-authored-by: Cursor <[email protected]>
Verifies that setModelMarkers is called for models that don't match
the current editor's URI, ensuring validation works in other Monaco
editors like the Test Step modal's JSON editor.

Co-authored-by: Cursor <[email protected]>
@Kiryous Kiryous requested a review from a team as a code owner February 4, 2026 16:17
@Kiryous Kiryous self-assigned this Feb 4, 2026
@Kiryous Kiryous added Team:One Workflow Team label for One Workflow (Workflow automation) (do not use) backport:9.3 This doesn't do backports! use `backport:version` `v9.3.0` instead release-note:skip release_note:skip Skip the PR/issue when compiling release notes and removed release-note:skip labels Feb 4, 2026
@Kiryous Kiryous changed the title Fix validation in Test Step modal by ensuring markers are set for all editors [One Workflow] Fix validation in Test Step modal by ensuring markers are set for all editors Feb 4, 2026
Copy link
Copy Markdown
Contributor

@rosomri rosomri left a comment

Choose a reason for hiding this comment

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

lgtm

@Kiryous Kiryous enabled auto-merge (squash) February 5, 2026 15:15
@elasticmachine
Copy link
Copy Markdown
Contributor

⏳ Build in-progress, with failures

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #139 / Agent Builder tools MCP tools creating MCP tools should create an MCP tool by selecting connector and tool
  • [job] [logs] FTR Configs #100 / Endpoint plugin @ess @serverless @skipInServerlessMKI Endpoint policy response api GET /api/endpoint/policy_response "before all" hook for "should return one policy response for an id"

History

cc @Kiryous

@Kiryous Kiryous merged commit 24aac0c into elastic:main Feb 6, 2026
17 checks passed
@kibanamachine kibanamachine added v9.4.0 backport missing Added to PRs automatically when the are determined to be missing a backport. labels Feb 6, 2026
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

8 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

27 similar comments
@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

@kibanamachine
Copy link
Copy Markdown
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 251714 locally
cc: @Kiryous

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

Labels

backport missing Added to PRs automatically when the are determined to be missing a backport. (do not use) backport:9.3 This doesn't do backports! use `backport:version` `v9.3.0` instead release_note:skip Skip the PR/issue when compiling release notes Team:One Workflow Team label for One Workflow (Workflow automation) v9.4.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants