fix(landing): trailing slash on working/staging/reviewing project links
These three are virtual party-aggregator folders — the trailing slash serves their dir_tool (the browse folder-nav listing of parties INSIDE the folder), while the no-slash form served the browse tool scoped at the project level. Land the user inside the folder. archive/ keeps the no-slash form (its default_tool is the archive tool, which is the intended landing there). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
49e8ea4b4f
commit
ec9c9c72bc
1 changed files with 6 additions and 3 deletions
|
|
@ -684,9 +684,12 @@
|
|||
var p = encodeURIComponent(project);
|
||||
var stages = [
|
||||
{ id: 'stageArchive', href: '/' + p + '/archive' },
|
||||
{ id: 'stageWorking', href: '/' + p + '/working' },
|
||||
{ id: 'stageStaging', href: '/' + p + '/staging' },
|
||||
{ id: 'stageReviewing', href: '/' + p + '/reviewing' },
|
||||
// working/staging/reviewing get a trailing slash so the user lands
|
||||
// INSIDE the folder (the dir_tool browse listing of parties),
|
||||
// not on the browse tool scoped at the project level.
|
||||
{ id: 'stageWorking', href: '/' + p + '/working/' },
|
||||
{ id: 'stageStaging', href: '/' + p + '/staging/' },
|
||||
{ id: 'stageReviewing', href: '/' + p + '/reviewing/' },
|
||||
];
|
||||
for (var i = 0; i < stages.length; i++) {
|
||||
var a = document.getElementById(stages[i].id);
|
||||
|
|
|
|||
Loading…
Reference in a new issue