chore: v2 - validation error if component failed to load#2438
Merged
maxy-shpfy merged 1 commit intoJun 19, 2026
Merged
Conversation
🎩 PreviewA preview build has been created at: |
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
8 tasks
7ab01b2 to
c246e88
Compare
74bfa7e to
94a9ddc
Compare
camielvs
approved these changes
Jun 19, 2026
Collaborator
Author
Merge activity
|
94a9ddc to
20497bb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Description
When a pipeline is loaded in the editor, tasks that reference external components (via URL, digest, or inline text) were not having their component specs resolved. This meant the editor had no live component spec to work with, and validation could not surface a meaningful error when a component failed to load.
This PR introduces a hydration step that runs immediately after a pipeline spec is deserialized. It walks every task in the spec, calls
hydrateComponentReferencefor any task that references a loadable component, and populatesresolvedComponentSpecon success. Tasks that already have asubgraphSpecare recursed into rather than re-hydrated at the top level.If hydration returns
null(e.g. the URL is unreachable or the component text is invalid), the task is left untouched and a newCOMPONENT_HYDRATION_FAILEDvalidation issue is raised. The issue resolution card surfaces a human-readable message directing the user to check the component URL or their connection and reload the pipeline.Related Issue and Pull requests
Type of Change
Checklist
Screenshots (if applicable)
Fix dialog:
Test Instructions
COMPONENT_HYDRATION_FAILEDissue appears.COMPONENT_HYDRATION_FAILEDvalidation error appears in the issues panel with the message prompting the user to check the URL or connection.Additional Comments
The
deserializeSpecDatahelper was extracted from the inline query function inuseLoadSpecto keep the hydrationawaitclean and to make the deserialization logic independently testable.