Guide hackathon event editors through tag setup

[DVidal1205]

Bug

Hackathon event editors see a disabled Create event button when the selected hackathon has no active event tags. The disabled control gives them no working route to satisfy the prerequisite.

Knight Hacks IX currently has no event tags, so this blocks its team from starting event setup even though the KH IX Team role has the hackathon event read, edit, and check-in permissions.

Expected behavior

Keep the primary action usable and route editors to event tag setup when no active tag exists.

[coderabbitai]

Coding Plan

Summary

• Replace the dead disabled "Create event" button with a control that routes to the Tags view when the selected hackathon has no active event tags.
• Reuse the existing sectionHref("tags") helper and Link/router already present in the workspace file. Add no new components or abstractions.
• Add tests for the three control states, since this behavior is currently untested.

Implementation Steps

Make the Create event control route to tag setup

This phase changes the primary action so editors always have a working route. When active tags exist, the button opens the create form as before. When no active tags exist but a hackathon is selected, the button routes to the Tags view instead of being dead.

Task 1: Route the Create event button to the Tags view when no active tags exist

Keep the primary action usable and send editors to tag setup when the prerequisite is unmet.

• Modify the "Create event" button block in apps/blade/src/app/_components/admin/hackathon-events/hackathon-events-workspace.tsx.
• Keep the button disabled only when !selectedHackathon. A hackathon must be selected for any action.
• When selectedHackathon is set and activeTags.length === 0, render the control as a route to the Tags view. Use the existing Link alias with sectionHref("tags") (for example <Button asChild><Link href={sectionHref("tags")}>...</Link></Button>), or call router.push(sectionHref("tags")) in the click handler. Prefer the Link form to match the existing <Button asChild><Link/></Button> convention in this file.
• When activeTags.length > 0, keep the current behavior: onClick={() => openForm("create")}.
• Update the button label and tooltip for the no-active-tags state so the text describes the route (for example label "Set up event tags" and tooltip "No active event tags. Set up tags first."). Reuse the existing tag-related copy where possible; keep terminology consistent with the Tags section.
• Do not change permission checks. The control stays inside the canEdit block.

Task 2: Add test coverage for the Create event control states

Add coverage for the new behavior, because no test currently asserts on this control.

• Add a test near apps/blade/src/tests/events/ (or a new file under apps/blade/src/tests/admin/) that renders the workspace with the relevant states.
• Assert that with activeTags.length === 0 and a selected hackathon, the control links to sectionHref("tags") and is not a dead disabled button.
• Assert that with activeTags.length > 0, the control opens the create form.
• Assert that with no selected hackathon, the control is disabled.

🤖 Prompt for AI agents

Fix the dead "Create event" button in
`apps/blade/src/app/_components/admin/hackathon-events/hackathon-events-workspace.tsx`.

- Change the disabled condition: disable the button only when
`!selectedHackathon`.
- When `selectedHackathon` exists and `activeTags.length === 0`: render the
button as a link to `sectionHref("tags")` using the existing `Link` alias
(`<Button asChild><Link href={sectionHref("tags")}>...</Link></Button>`), or use
`router.push(sectionHref("tags"))` in an `onClick` handler. Prefer the `Link`
form since it matches the existing `<Button asChild><Link/></Button>` pattern in
this file.
- When `activeTags.length > 0`: keep the current `onClick={() =>
openForm("create")}` behavior unchanged.
- Update the label and tooltip text for the no-active-tags state to describe the
route (for example, label "Set up event tags", tooltip "No active event tags.
Set up tags first."). Reuse existing tag-related copy where possible and keep
terminology consistent with the Tags section.
- Do not touch permission logic: keep the control inside the existing `canEdit`
block.

Add test coverage since none exists for this control:

- Add a test file near `apps/blade/src/tests/events/` or under a new
`apps/blade/src/tests/admin/` path.
- Test case 1: `activeTags.length === 0` with a selected hackathon — assert the
control links to `sectionHref("tags")` and is not a disabled dead button.
- Test case 2: `activeTags.length > 0` — assert the control opens the create
form.
- Test case 3: no selected hackathon — assert the control is disabled.

Research

The hackathon events admin workspace lives in apps/blade/src/app/_components/admin/hackathon-events/hackathon-events-workspace.tsx. It computes activeTags from api.hackathonEvent.listTags, and disables the "Create event" button when activeTags.length === 0, showing the tooltip "Create or import an active event tag first." The file already has a local sectionHref(view) helper that builds URLs for the view search param (including sectionHref("tags")), an imported RouteTransitionLink as Link, and a router from useNavigationRouter. The Tags view renders EventTagManagement and HackathonTagImportDialog, where editors create or import tags. No tests currently assert on the button's disabled state or tooltip.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Fix the dead "Create event" button in
`apps/blade/src/app/_components/admin/hackathon-events/hackathon-events-workspace.tsx`.

- Change the disabled condition: disable the button only when
`!selectedHackathon`.
- When `selectedHackathon` exists and `activeTags.length === 0`: render the
button as a link to `sectionHref("tags")` using the existing `Link` alias
(`<Button asChild><Link href={sectionHref("tags")}>...</Link></Button>`), or use
`router.push(sectionHref("tags"))` in an `onClick` handler. Prefer the `Link`
form since it matches the existing `<Button asChild><Link/></Button>` pattern in
this file.
- When `activeTags.length > 0`: keep the current `onClick={() =>
openForm("create")}` behavior unchanged.
- Update the label and tooltip text for the no-active-tags state to describe the
route (for example, label "Set up event tags", tooltip "No active event tags.
Set up tags first."). Reuse existing tag-related copy where possible and keep
terminology consistent with the Tags section.
- Do not touch permission logic: keep the control inside the existing `canEdit`
block.

Add test coverage since none exists for this control:

- Add a test file near `apps/blade/src/tests/events/` or under a new
`apps/blade/src/tests/admin/` path.
- Test case 1: `activeTags.length === 0` with a selected hackathon — assert the
control links to `sectionHref("tags")` and is not a disabled dead button.
- Test case 2: `activeTags.length > 0` — assert the control opens the create
form.
- Test case 3: no selected hackathon — assert the control is disabled.

💡 Iterate on the plan with: `@coderabbitai` <feedback>

Example Feedback
- `@coderabbitai` You can skip phase 3. Add a simple unit test case for phase 2.
- `@coderabbitai` For design choice 1 go ahead with option 3 and replan.

---