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

Feature Request: Tabular Data

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
javascript, react

调研方向

该 issue 将 mobx-react-devtools 的 log 函数和 Chrome DevTools 列为起点;检查当前的日志记录如何记录 actions、computations 和 renders。为每次 update 定义一个包含计数、平均耗时和总耗时的单一摘要,然后验证输出在不锁死控制台的情况下仍然可用。

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

描述

I currently have a project that can render tens of thousands of elements. I use observable objects with sideways loading to render items very fast, however, changes that affect all the elements can take 2-4 seconds (unacceptable for UI purposes). I have a lot of options to optimize, but knowing what is taking the most time would help to peel the onion. I can use chrome devtools to show that most of the time is spent in scripting, but I don't know if that is my code, mobx, or react diffing. If I try to use the the mobx-react-devtools log function, it generates so many log statements to the console that it locks up chrome for a long time. Even if I wait for them to catch up, it is too much data to sift through. Would it be possible to implement a tabular data feature that generates only one log statement after each update? Something like an object that lists what actions/computations/renders were performed, how many times each was performed, and ave & total times for each would be awesome. I am doing something similar in my code ad-hoc but it is very intrusive into my code and makes things less manageable.

主要语言
JavaScript
星标
1.2k
派生
45
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

mobxjs/mobx-react-devtools 的其他 Issue

查看 mobxjs/mobx-react-devtools 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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