-
Bug
-
Resolution: Done
-
Normal
-
1.9.0
-
None
-
1
-
False
-
-
False
-
Form widgets now support fetch:error:ignoreUnready to avoid surfacing errors while dependencies are incomplete, and fetch:response:default to provide immediate fallback defaults.
-
Bug Fix
-
-
-
RHDH F&UI plugins 3285
Description of problem:
When using widgets (ActiveDropdown, ActiveTextInput, ActiveMultiSelect, SchemaUpdater) with fetch:retrigger dependencies, the initial fetch often fails because the dependent fields don't have values yet. This results in HTTP errors (e.g., 404, 400) being displayed to the user on the form, even though this is expected behavior during initial load.
Add a new ui:props option fetch:error:skip that suppresses fetch error display until all fetch:retrigger dependencies have values.
- duplicates
-
RHDHBUGS-2452 [Orchestrator] Add fetch:error:skip option to suppress expected fetch errors during initial load
-
- Closed
-
- is related to
-
RHIDP-11066 Orchestrator Form Field Visibility & Custom Review Components
-
- Dev Complete
-