Skip to content

[Studio] Render the configuration editor from a configuration it is given - #691

Draft
markus-moser wants to merge 2 commits into
2026.xfrom
feat/detail-view-config-source
Draft

[Studio] Render the configuration editor from a configuration it is given#691
markus-moser wants to merge 2 commits into
2026.xfrom
feat/detail-view-config-source

Conversation

@markus-moser

Copy link
Copy Markdown
Contributor

DataImporterDetailView both fetched the configuration and rendered it, so the tab tree could only ever show what the detail endpoint returned for the current user.

This splits the two. DataImporterConfigEditor owns the form, the tabs and useDetailView, over a configuration it is handed. The detail view keeps the RTK query, the permission derivation and the save mutation, and passes the toolbar in through a render prop, because isDirty and the save handler only exist inside the form.

No behaviour change: same tabs, same toolbar, same BaseDetailView props.

Gates

Gate Result
npm run check-types 0 errors
npm run lint 0 errors

Verified in the running app against the car-import configuration — General, Data Setup (all five steps), Execution and Permissions all render as before, with no server errors.

🤖 Generated with Claude Code

markus-moser and others added 2 commits September 9, 2026 16:15
…iven

The detail view both fetched the configuration and rendered it, so the tab tree
could only ever show what the detail endpoint returned.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@sonarqubecloud

sonarqubecloud Bot commented Sep 9, 2026

Copy link
Copy Markdown

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.

2 participants