"explorer.fileNesting.operateAsGroup" weird setting and weirder semantics

[isidorn]

Testing #145640

imho all operations on the parent resource should affect the child resource. Same as with folders.
Why do we make this configurable? Do users actually not expect this and want to change this? Why is the default false?

If we really decide that a setting for this is needed then operateAsGroup is misleading because it is not actually a group. All operations on the child are not done on the parent.

[JacksonKearl]

The main problem I saw was how do we make it possible to only copy the single file when you copy a parent. One idea I considered was making the nest operate as a group when it's collapsed, but individual files when it's expanded? That way you would:

1. collapse the nest and copy it as one item always,
2. expand the nest and select the subset of entries you want to copy
3. expand the nest and select just the parent, then only operate on the parent.

what would you think of that flow?

A slight issue there at the moment is the model doesn't know anything about the view's collapse state.

[JacksonKearl]

Enabled the operateAsGroup setting by default though

[isidorn]

@JacksonKearl I like your suggestion to distinguish if collapse or expand and based on that to change behaviour.

[tanhakabir]

Getting explorer.fileNesting.operateAsGroup as undefined setting on:

Version: 1.67.0-insider (Universal)
Commit: 7fc8af4
Date: 2022-04-28T05:19:19.018Z
Electron: 17.4.1
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Darwin x64 21.4.0

[JacksonKearl]

Setting is removed sorry. New intended behavior is that it operates as group when collapsed.