Uploaded image for project: 'Red Hat Developer Hub Bugs'
  1. Red Hat Developer Hub Bugs
  2. RHDHBUGS-2454

[orchestrator] Add fetch:response:default for static fallback default values

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • 1.9.0
    • 1.9.0
    • Orchestrator, UI
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False
    • RHDH F&UI plugins 3285

      Description of problem:

       

      Currently, widgets require a fetch:response:value selector to set a default value, which means a fetch call must succeed for any default to be applied.There are scenarios where:

      • You want a static fallback default when the fetch fails or hasn't completed yet
      • You want to pre-populate a field with a known value without requiring a fetch at all
      • The fetch depends on other fields (fetch:retrigger) that aren't filled yet, but you still want an initial default

      Add a new ui:props option fetch:response:default that provides a static default value applied immediately on widget mount, acting as a fallback when fetch fails or hasn't completed, and gets overridden by fetch:response:value once fetch succeeds.

              rh-ee-lprabhu Lokananda Prabhu
              rh-ee-lprabhu Lokananda Prabhu
              RHDH Frontend Plugins & UI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: