Make Storage changes readable in a narrow docked panel

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
领域
frontend

调研方向

The payload names no files or components, so start by finding the Storage view in the docked panel UI and reproducing it at a narrow width. Check how the Changes and Browse views lay out long keys and values, and how live updates reach the Changes list. Done when change details are readable at a typical docked width, there is a way to open a change in a larger view, and live updates keep the user in Changes.

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

描述

enhancement

What happened

Storage showed the expected changes to Experimenta's data. In the docked T3 Code panel, the presenter could not make the Changes detail larger and switched to Browse for a readable JSON view. At the narrower width they would use during daily work, the Storage controls and content looked cramped.

Make change details readable at typical docked widths and provide a way to inspect a change in more space. Verify that long keys and values remain accessible and that users can stay in Changes when inspecting a live update.

主要语言
C++
星标
243
派生
21
平均合并
15 小时 6 分钟
30 天内合并 PR
57

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

callstackincubator/codex-mobile-dev-plugin 的其他 Issue

查看 callstackincubator/codex-mobile-dev-plugin 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

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