Feature Request: Tabular Data
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- developer-experience, tooling
Research direction
The issue names the mobx-react-devtools log function and Chrome DevTools as the starting points; review how logging currently records actions, computations, and renders. Define a single summary per update with counts and average and total times, then verify that the output remains usable without locking up the console.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mobxjs/mobx-react-devtools
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mobxjs/mobx-react-devtools#119 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
mobxjs/mobx-react-devtools#118 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mobxjs/mobx-react-devtools#117 · 3 comments · 13 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mobxjs/mobx-react-devtools#116 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
mobxjs/mobx-react-devtools#115 · 3 comments ·
All issues in mobxjs/mobx-react-devtools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Add: Atlas TVOpenchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 4 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jaegertracing/jaeger-ui#4547 · 3 comments ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#4090 ·
Maintainers usually reply within 1 day
-
bug deck: add to staging level: missing p-feature: Manage Submissions p-feature: Submissions and process priority: MUST HAVE ready for dev lead role: missing size: missing time sensitive
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hackforla/tdm-calculator#3581 ·
Maintainers usually reply within 2 days