Collapse and Expand DevTools Tree Nodes

[noi5e]

DevTools nodes now accordion open and closed.

Screen.Recording.2022-07-21.at.10.15.59.PM.mov

---

Developer Tools Web Extension Planning Issue: #2127

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
lexical	✅ Ready (Inspect)	Visit Preview	Jul 22, 2022 at 7:08PM (UTC)
lexical-playground	✅ Ready (Inspect)	Visit Preview	Jul 22, 2022 at 7:08PM (UTC)

[zurfyx]

LGTM!

[thegreatercurve]

Nic work @noi5e!

[noi5e]

Pushed some new commits to take care of everyone's comments including this one:

Should this default to 0? Is there a case where you'd want to start at something other than zero other than in the implementation? Probably not a big deal since this isn't exported or anything.

I rewrote depthFirstSearch with default parameters, and also passing in nodeMap as an additional parameter. Seems like a better piece of code, thanks for the suggestion:

  const depthFirstSearch = (
    map: DevToolsTree = nodeMap,
    nodeKey = 'root',
    depth = 0,
  ): DevToolsNode => {
    const node = map[nodeKey];
    const children: Array<DevToolsNode> = [];

    if (Object.prototype.hasOwnProperty.call(node, '__children')) {
      node.__children.forEach((childKey: string) => {
        children.push(depthFirstSearch(map, childKey, depth + 1));
      });
    }

    return {
      ...node,
      __type: node.__type,
      children,
      depth,
      lexicalKey: node.__key,
    };
  };

[noi5e]

This seems merge-ready, just failing some unrelated e2e tests in lexical-playground. This is the based on the most recent main as far as I know...