kawa/Ready2Blob
1
0
Fork 0
Code Issues Pull Requests Actions Packages Activity

docs(13-04): complete RemoteConfigStep full backend integration plan

Browse Source 
- 13-04-SUMMARY.md: all 18 backends wired, 6 new tests, 282/282 pass
- STATE.md: session updated, decisions recorded, progress 100%
- ROADMAP.md: phase 13 marked complete (4/4 plans)
- REQUIREMENTS.md: REMOTE-05 marked complete
This commit is contained in:
kawa
2026-04-01 16:59:38 +02:00
parent 2c596c96a0
commit 46b149d900
4 changed files with 132 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.planning/REQUIREMENTS.md
+1 -1
View File
@@ -49,7 +49,7 @@
- [x] **REMOTE-02**: BackendType is derived from registry keys (`keyof typeof BACKEND_REGISTRY`) instead of an explicit union literal, eliminating a touch-point when adding backends
- [x] **REMOTE-03**: BackendSelectionStep displays backends grouped by category (Cloud Object Storage, Cloud Drives, Protocol-based) with instant search filtering and inline SVG icons
- [x] **REMOTE-04**: OAuth-token backends (Google Drive, Dropbox, Box, pCloud, OneDrive) display a collapsible OAuthInstructions component with backend-specific `rclone authorize` command
- [ ] **REMOTE-05**: RemoteConfigStep renders the correct form fields for every backend, including GdriveAuthToggle for Google Drive's dual-auth (OAuth token vs service account)
- [x] **REMOTE-05**: RemoteConfigStep renders the correct form fields for every backend, including GdriveAuthToggle for Google Drive's dual-auth (OAuth token vs service account)
- [x] **REMOTE-06**: buildRcloneConf produces valid rclone.conf output with correct type strings for all 18 backends
## Future Requirements