maximus/Simpl-Resultat
1
0
Fork 0
Code Issues 19 Pull requests 8 Projects Releases 34 Packages Wiki Activity Actions

fix(import): name a source after its subfolder, read-only (#426) #441

Merged
maximus merged 3 commits from issue-426-source-name-folder into main 2026-10-16 00:37:20 +00:00
Conversation 3 Commits 3 Files changed 13 +180 -24

3 commits

Author SHA1 Message Date
le king fu
e177a7561f docs(import): changelog, guide, architecture and QA cases of the read-only source name
All checks were successful
PR Check — Frontend / frontend (pull_request) Successful in 1m56s
Details 
Resolves #426

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-13 21:08:07 -04:00
le king fu
00b4319c44 test(import): pin the read-only source name of the configuration panel 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-13 21:06:07 -04:00
le king fu
ed3a4bb9a0 fix(import): name a source after its subfolder, read-only 
The source name typed during configuration was saved, but the next import
looks the source and its imported files up by the subfolder name, so a
renamed source looked new: format guessed again, every file pre-checked,
and a second source created under the folder name.

The name field becomes a read-only SourceNameDisplay showing the subfolder
name with a hint, and executeImport writes selectedSource.folder_name on
create and update, whatever config.name holds, behind a selectedSource
guard. The import card sentence no longer asks to check the source name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-13 21:05:46 -04:00