Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[P1] frontend: Complete ADR-007 feature route mapping

未关闭
#222 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
typescript
领域
api, frontend

调研方向

从 docs/adr/007-frontend-modernization.md、frontend/README.md、frontend/app/evaluation/page.tsx 和 frontend/components/Configuration/Cases.tsx 开始;在修改路由之前,梳理现有的导航和服务/API 依赖关系。检查相关 issue #123、#147 和 #143 以了解约束条件。当所需的路由和界面已实现或有意移除、文档已更新,并且 pnpm --dir frontend lint 和 build 通过时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

frontend priority:P1 type:feature

Problem inventory

ADR-007 defines required frontend capabilities that are only partially mapped today. Some routes redirect to utility/config pages, some expected routes are absent, and one configuration component is empty.

Type: feature gap / integration regression risk

Evidence

  • docs/adr/007-frontend-modernization.md specifies /evaluation, /evaluation/[runId], and /avatar/settings.
  • frontend/app/evaluation/page.tsx only redirects to /configuration/evaluation; there is no dedicated EvalDashboard or /evaluation/[runId] run viewer.
  • frontend/app/avatar/settings is absent, while ADR-007 expects avatar parameter selection persisted through PUT /api/avatar/config.
  • frontend/components/Configuration/Cases.tsx is an empty stub while configuration navigation exposes cases.
  • frontend/README.md says the UI covers Avatar, Chat, Essays, Questions, Configuration, Upskilling, Evaluation, LMS Gateway, and APIM-routed backend traffic, so route mapping must be complete and trustworthy.

Impact assessment

User impact: high. New functionality appears present in documentation/navigation but is not consistently reachable as mature product UI.
Blast radius: frontend routes, workspace navigation, API client integration, and service-contract expectations.

Acceptance criteria

  • Produce a route-to-capability map for all public, workspace, and configuration routes, including which backend service/API path each route depends on.
  • Implement or finalize a mature /evaluation dashboard for run history, quality trends, dataset visibility, and degraded-state status.
  • Implement /evaluation/[runId] for per-run details using the evaluation service contract.
  • Implement /avatar/settings with voice, language, speaking style, avatar style, response length, and expertise level controls; persist with PUT /api/avatar/config when the backend route is available or define the exact backend contract if missing.
  • Replace the empty cases stub with a mature cases management surface or remove the entry from navigation with documented rationale.
  • Ensure every workspace navigation item resolves to a real page with role-appropriate copy and no unexpected redirect to a configuration utility page unless intentionally documented.
  • Update frontend README or modernization docs with the completed route map and any deferred gaps.
  • pnpm --dir frontend lint and build pass.

Agent assignment

Primary specialist: TypeScriptDeveloper
Architecture validation: SystemArchitect
UI validation: UIDesigner

Dependency notes

This should precede broad UI cleanup where route removal/retirement is being considered.

Related backlog

  • #123 avatar restructuring may affect the settings implementation.
  • #147 avatar runtime incident is related to service readiness, not the settings UI itself.
  • #143 touches frontend evaluation/history display quality.
主要语言
Python
星标
17
派生
8
PR 合并指标
30 天内没有已合并 PR

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Azure-Samples/tutor 的其他 Issue

查看 Azure-Samples/tutor 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。