[Help Wanted] No expand/collapse button in workspace viewer

[TTTPOB]

my situation

normal situation

[ElianHugh]

What is your level of detail setting? It looks like it's on minimal rather than detailed. See: r.session.levelOfObjectDetail

[TTTPOB]

Thank you for the quick answer! I don't know there is a setting controls this before.
It solved my problem, thank you.

[ElianHugh]

No worries! If you ever have any questions feel free to ask or check out the wiki! All the best

[danielbasso]

I've been thinking for some time to suggest that the default option for vsc.str.max.level should be 2. I think it's way more probable that a person would like it to be fully expandable then not. @ElianHugh , what do you think?

[renkun-ken]

vsc.str.max.level=2 has some significant performance issue if user loads a data of many columns, a list of many elements, or nested levels in the R session. Currently, we write all column information to {tempDir}/workspace.json on each top-level user input via a task callback. We had that for some while but revert to 0 for lower delay of user input.

[ElianHugh]

Right, yeah, it was a concious decision due to significant performance issues for some users whenever the callback occurred. IIRC, this was chosen around the same time as the object limit was implemented

[lukesdm]

It seems calling options(vsc.str.max.level = 2) in the current version of VS Code with this extension breaks the Workspace viewer.

Example: trying to expand 'my_variables'.

Before:

After:

Environment:

• VS Code 1.67.2
• REditorSupport 2.5.0
• Windows 10

Edit: I see similar behavior with changing r.session.levelOfObjectDetail to non minimal. It could be related to my data - I'm dealing with geospatial shp files.