Skip to content

fix(launch): render object map values as JSON instead of crashing on relaunch#922

Open
1fanwang wants to merge 1 commit into
flyteorg:masterfrom
1fanwang:fix-mapinput-object-render
Open

fix(launch): render object map values as JSON instead of crashing on relaunch#922
1fanwang wants to merge 1 commit into
flyteorg:masterfrom
1fanwang:fix-mapinput-object-render

Conversation

@1fanwang

@1fanwang 1fanwang commented Jun 21, 2026

Copy link
Copy Markdown

TL;DR

Relaunching an execution whose input is a Map[str, Struct] breaks the launch form: the map's object values render as [object Object], the inputs are flagged invalid, and Launch is disabled — so you can't relaunch at all.

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Complete description

The map's values are objects, but parseMappedTypeValue drops each one straight into a text field, where it stringifies to [object Object] and trips a render error. The field is typed string, so the fix belongs at the parse boundary, not the JSX: JSON-stringify object values as the map is parsed, so the field, its validation, and the round-trip back to a literal all see a string. Plain strings and numbers pass through untouched.

Smoke-tested on a live console: relaunch an execution with a map<string, struct> input. Before, the value fields read [object Object], are flagged invalid, and Launch is disabled; after, they read {"nested":"bar"} / {"k":1} and Launch works. MapInput.test.tsx covers it.

Tracking Issue

NA

Follow-up issue

NA

…relaunch

A map whose values are objects (e.g. Map[str, Struct]) parsed each value into the
string-typed value field, so the launch form bound an object straight into a text
input -- coerced to "[object Object]" and producing render errors on relaunch.
JSON-stringify object values at parse time so the field always receives a string.

Signed-off-by: 1fanwang <1fannnw@gmail.com>
@welcome

welcome Bot commented Jun 21, 2026

Copy link
Copy Markdown

Thank you for opening this pull request! 🙌

These tips will help get your PR across the finish line:

  • Most of the repos have a PR template; if not, fill it out to the best of your knowledge.
  • Sign off your commits (Reference: DCO Guide).

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.

1 participant