daniel/deepdrft
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 13 Wiki Activity

docs(Releases.razor): correct stale medium-tab comment — tabs are explicit markup, not enum-driven; adding a medium requires a hand-added panel in enum order

Browse Source
This commit is contained in:
daniel-c-harvey
2026-06-17 14:27:50 -04:00
parent 13fbcc2d43
commit 23a1275025
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DeepDrftManager/Components/Pages/Tracks/Releases.razor
+5 -4
View File
@@ -54,10 +54,11 @@
</MudStack>
</MudStack>
@* Medium tab strip: an ALL tab plus one tab per ReleaseMedium, ALL left-most. The medium tabs are
enum-driven — a fourth medium adds a tab automatically; only a label-lookup entry (MediumTabLabels)
and a content arm (MediumGrid) are needed, no markup fork. Selecting a tab swaps the grid below in
place. *@
@* Medium tab strip: an ALL tab plus one explicit MudTabPanel per ReleaseMedium, ALL left-most. Each
panel is hand-declared in markup (not enum-driven) so @ref captures of the per-tab grid components
are possible. Adding a future medium requires a hand-added MudTabPanel; its position in markup must
match ReleaseMedium enum order, since the ?medium= deep-link seed and ActiveMedium getter are
position-based (panel 0 = ALL, panels 1.. = enum values in order). *@
@* Medium-aware Add Track: the button reflects the active tab and pre-selects the upload form to that
tab's medium via a single query-param (?medium=…); the ALL tab defaults to Cut. The medium is a seed
only — the upload form's selector stays user-changeable after landing. *@