[Studio] Load live preview column headers in resolver & processing steps#639
Merged
Conversation
markus-moser
force-pushed
the
fix/resolver-step-live-column-headers
branch
from
2e28e68 to
9283ff8
Compare
The resolver and processing steps' Data Source Index selects read columns from configData.columnHeaders, which reflects only the persisted config — running a preview does not invalidate that query, so the selects stayed empty until a save/reload. Add a shared useColumnHeaderOptions hook that loads the columns live from the current loader/interpreter config (the endpoint the mapping step uses). data-setup-tab owns a previewVersion counter that the preview step bumps on copy-from-source and upload; the hook refetches when it changes, so columns stay in sync with the preview data without refetching on every visit. Config changes refetch on their own via the query key.
markus-moser
force-pushed
the
fix/resolver-step-live-column-headers
branch
from
8294b20 to
6e47349
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Changes in this pull request
The "Data Source Index" selects in the resolver and processing steps read their columns from
configData.columnHeaders, which only reflects the persisted config — running a preview doesn't invalidate that query, so the selects stayed empty until a save/reload.Add a shared
useColumnHeaderOptionshook that loads the columns live from the current loader/interpreter config (the same endpoint the mapping step uses), and use it for both steps. Also removes the duplicated header-mapping that lived in both components.Additional info
Related to #637