aksd: pass setSelectedTab to project header action components

[gambtho]

Summary

• Extend ProjectHeaderAction interface to pass setSelectedTab as a prop to header action components
• This gives plugins a type-safe way to switch project detail tabs (e.g. navigating to the Deploy tab after pipeline setup completes)
• Replaces the previous DOM CustomEvent approach with proper React prop-based data flow

Type of Change

• New feature (non-breaking change which adds functionality)

Changes Made

• projectsSlice.ts — Added setSelectedTab?: (tabId: string) => void to ProjectHeaderAction.component props interface
• ProjectDetails.tsx — Pass setSelectedTab when rendering header action components

Why props over DOM events

• Type-safe: TypeScript enforces the contract between Headlamp and plugins
• Follows React data flow: props flow down through the component tree instead of bypassing React via window.dispatchEvent
• Less coupling: plugins call a function they receive as a prop rather than dispatching magic-string events

Testing

• Unit tests pass
• Manual testing completed

Test Cases

1. Header action component receives setSelectedTab prop
2. Calling setSelectedTab('deploy') switches to the Deploy tab
3. Calling with an invalid tab ID updates state (tab rendering handles missing tabs gracefully)

Related to

• Pipeline wizard UX: consolidate review steps into single tab #408

[Copilot]

Pull request overview

Adds a DOM-event-based mechanism for external UI components to programmatically change the selected tab on the Project Details page.

Changes:

• Introduces a window event listener (navigate-to-deploy-tab) that reads a CustomEvent.detail value as the target tab ID.
• Updates the selected tab state when a valid tab ID is received.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[illume]

I don't know if this is the best way to do this... I asked for a review from @sniok Maybe a separate API would be good here... or maybe it's just fine.

I think it's ok, and doing it via an API might take much longer to implement, so approving.

[gambtho]

I don't know if this is the best way to do this... I asked for a review from @sniok Maybe a separate API would be good here... or maybe it's just fine.

I think it's ok, and doing it via an API might take much longer to implement, so approving.

I don't mind trying it that way too -- this doesn't seem urgent, if you'd prefer a different approach

[gambtho]

I don't know if this is the best way to do this... I asked for a review from @sniok Maybe a separate API would be good here... or maybe it's just fine.
I think it's ok, and doing it via an API might take much longer to implement, so approving.

I don't mind trying it that way too -- this doesn't seem urgent, if you'd prefer a different approach

yeah -- this seems much better, glad you said something

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[sniok]

I'd expose ProjectDetailsContext to plugins, it already has setSelectedTab there.
But passing it to header action directly is fine too.

[illume]

Thanks! 🎉