Should `reactiveValues` be grouped?

Open
#54 4 comments 0 reactions 0 assignees View on GitHub

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
Domain
devtools

Research direction

Start by tracing how the current graph represents each reactiveValues key, names(obj), and as.list. Clarify whether a master reactiveValues node and its proposed child nodes are required, and define the ready-state and hierarchy behavior before implementation. Done means the grouping decision is agreed and reflected consistently in the visualizer.

Written by the indexing model from the issue text.

Description

Currently each key is a separate node. names(obj) is a separate node.

Should there be a master reactiveValues node (always in a ready state) that has a child nodes of keys and child nodes for as.list or names?

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.