MemberJunction / MemberJunction/MJ

Migrate AI Agent Run form's hand-rolled tab bar to mj-tab-nav

Open
#3,359 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TSQL
Stars
29
Forks
6
Avg merge
2d 1h
Merged PRs (30d)
323

Description

The AI Agent Run form (`packages/Angular/Explorer/core-entity-forms/src/lib/custom/ai-agent-run/ai-agent-run.component.*`) uses a hand-rolled tab bar that predates `mj-tab-nav`. Per the "spot a hand-rolled primitive → file the two-step issue, don't expand your PR" convention, PR #3296 added its new Branches tab following the existing local pattern instead of migrating the bar.

Follow-up: migrate the form's tab bar (Timeline / Visualization / Analytics / Details / Branches) to `mj-tab-nav` from `@memberjunction/ng-ui-components`, preserving the lazy `*Loaded` boolean pattern per tab.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Contributor guide

Open the contributing guide

Research direction

Start with packages/Angular/Explorer/core-entity-forms/src/lib/custom/ai-agent-run/ai-agent-run.component.* and inspect the current Timeline, Visualization, Analytics, Details, and Branches tab implementation alongside the mj-tab-nav API from @memberjunction/ng-ui-components. The work is done when the form uses mj-tab-nav and each tab preserves its lazy *Loaded boolean behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.