Implement the terminal user interface of the `mithril-setup signer` command

未关闭
  • 哪里不对？
#3,699 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
cli

调研方向

Start in the mithril-setup crate, where ratatui is already added and the signer sub-command is wired, and read ADR 014 (https://mithril.network/doc/adr/14) for the intended form layout. The open work is the form screen (parameter table, in-place editing, buttons), the result screen with the install command, and an undecided error-handling approach. Done means both screens render from the setup orchestrator's output and the README documents them. Ask the maintainers about the error-handling choice before building it.

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

描述

feature :rocket:

Why

The mithril-setup signer command must guide the operator through the setup of a Mithril signer in a terminal, with every parameter prefilled and editable in a single view, as decided in ADR 014 (https://mithril.network/doc/adr/14).

What

The mithril-setup signer command shows a form screen (a grid of the prefilled parameters with their provenance and status, editable in place) and a result screen (the install command to run), built with ratatui and driven by the setup orchestrator.

How

  • Add ratatui to the mithril-setup crate
  • Implement the form screen
    • Banner with the messages of the command
    • Table of the parameters with their value, provenance and status
    • Row selection, in place editing
    • Message of the selected row and key help
    • Abort and Continue buttons
  • Implement the result screen with the install command, the warnings line and the Exit button
  • How do deal with errors? (new screen or crash the TUI with error in the console, overwriting an existing file)
  • Wire the terminal interface in the signer sub-command
  • Document the screens in the mithril-setup README
  • Next fine tuning steps:
    • TBD
主要语言
Rust
星标
155
派生
52
平均合并
2 天 17 小时
30 天内合并 PR
37

环境准备

从这里开始

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

IntersectMBO/mithril 的其他 Issue

查看 IntersectMBO/mithril 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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