Repository navigation
feat: call the unfiled tracks To sort, and say WaveFlow keeps the list - #306
Conversation
Unfiled read as a folder that could be renamed, or as one holding uploads. It is the list of every track in no folder, kept by WaveFlow: it is now named To sort (À ranger), drawn with a tray rather than a folder and an Automatic badge, and its view says a track leaves it once filed and that it cannot be renamed or deleted. The delete confirmation, the delete notice and the upload lines say where tracks go back to. Signed-off-by: InstaZDLL <github.105mh@8shield.net>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
On the dev server, the owner found Unfiled unclear. It read as a folder like the others, one that could be renamed, or as the place uploads land. It is neither: it is the list of every track in no folder, and WaveFlow keeps it itself. It is renamed To sort (French: À ranger), the owner's choice.
What changes (web client only)
filed.unfiledreads "To sort" / "À ranger" everywhere it shows: its card, its view's title, the trail, the folder picker's first entry when filing a track, and the "filed in" notice.inboxicon) instead of a folder;.folder-badge) sits next to its name;The API keeps
unfiled(unfiled_track_count,…/folders/unfiled/tracks): this is a label change, not a contract change.Checked in a dark-theme screenshot of the root on desktop and mobile.
Tests
Playwright strings follow the new labels. The filing test also checks the Automatic badge on the To sort card, and fails when the badge is emptied (checked on a build that compiles).
Validation
refresh.css),tsc, 190 unit tests, buildSummary by CodeRabbit