Devtools (reactive graph visualization) in the playground
还没有人认领这个 Issue。
- #124 来自 @thetarnav —— 已关闭，未合并
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- babel, typescript
调研方向
首先检查 playground 当前如何在生产模式下运行，以及其 UI 是如何组织的。然后检查链接的 debugger 和 Babel transform 包，以确定图跟踪的集成点和阻碍因素。当已经确定 dev mode、debugger 附加、可选 transform 和图面板的架构与实现计划后，即可视为完成。
由索引模型根据 Issue 内容生成。
描述
I don't have anything prepared—this is just theoretical, but would it be possible to include a reactive graph debugger in the playground in the future?
One thing for certain—it would require the playground to work in a dev mode. And from what I know, it works in prod mode currently. This alone might just prevent this from happening. But would there be any other blockers?
This idea just popped into my head, and I wanted to ask if it would make sense and what should I take into consideration when architecting the devtools if it does.
Besides the solid operating in dev mode requirement, there are three parts of the devtools that I would need to think, about how'd they fit in:
- the debugger - the debugger would need to be attached to the application in the background, for the devtools to be able to get and track the state of the graph
- babel transforms - this one is not necessary, but useful, it'll allow for things like tracking stores, automatically naming signals/memos/stores, and tracking component props.
- the devtools/graph panel - part of the UI would need to be reserved for the devtools - for displaying the graph, toggling is on and off, configuring, etc.
I'm currently writing the devtools in a way that theoretically should allow it to be used in various places—not limited to the chrome extension. But some changes might be necessary. It's definitely not ready now. Not even close.
Still, I think it would be great to see the graph right in the playground eventually. So I just wanted to know what you think.
- 主要语言
- TypeScript
- 星标
- 246
- 派生
- 71
- 平均合并
- 5 分钟
- 30 天内合并 PR
- 6
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
solidjs/solid-playground 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 48/100
solidjs/solid-playground#194 ·
-
难度 3/5 1-2 天 新手友好度 35/100
solidjs/solid-playground#190 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 25/100
solidjs/solid-playground#179 · 2 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 38/100
solidjs/solid-playground#176 ·
-
难度 4/5 3-5 天 新手友好度 35/100
solidjs/solid-playground#175 ·
查看 solidjs/solid-playground 的全部 Issue
相似的 Issue
-
Phone app shows Unknown for a remote machine whose key changed可能已有人在做 @janicduplessis 今天认领。 未关闭area: mobile priority: P3 type: bug
难度 1/5 1 小时以内 新手友好度 78/100
appandflow/stim#5006 · 1 条评论 ·
维护者通常 1 天内回复
-
Area - Local to Cloud Bug
难度 2/5 1-3 小时 新手友好度 66/100
microsoft/vscode-mssql#23209 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
code-yeongyu/senpi#5713 · 1 条评论 ·
维护者通常 1 天内回复
-
A-linter
难度 2/5 1-3 小时 新手友好度 73/100
oxc-project/oxc#28783 ·
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 84/100
lingdojo/kana-dojo#33553 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复