Export reactlog

Open
#37 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
data-visualization

Research direction

The issue does not name a file or test. Start by tracing how reactlog currently renders and retains its data in the browser, then determine an export or non-browser access point. Done means a large reactlog can be recovered and inspected without relying on the web visualization.

Written by the indexing model from the issue text.

Description

My shiny app is so large that the reactlog is unresponsive and hangs for several minutes trying to render every step of a zoom - is there a way to save the reactlog and open it in another program? I am more than happy to even parse it by text without any kind of visualization, but I need some way to access it without a web browser. In its current implementation I can neither recover the data nor use it when debugging my app.

Dominant language
JavaScript
Stars
131
Forks
8
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rstudio/reactlog

All issues in rstudio/reactlog

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.