[Enhancement] Unify behavior when a folder is selected

[goran-w]

• When selecting a folder in Local Changes (Show as filesystem tree), the page "Select file to view changes" is displayed.
  • Special-case: when the selected folder has only a single file/item listed beneath it, that file's content is displayed instead. This breaks the pattern and can be a bit confusing to the user. IMHO, it would be better to be consistent and always show the same kind of page for a folder!
• When selecting a folder in History - Files (for a commit in log-graph), then an empty page is displayed. This is inconsistent with how the filesystem tree behaves in Local Changes. A simple fix for this would be to re-use the same page as in Local Changes, but simply replace its text with "Select file to view contents" (based on some input-param isChangeList or similar).
  • (It also doesn't have the single-file special-case from that other view, which IMHO is a good thing...)
• NOTE: An alternative solution would be to always display a (new) page "Folder" (+ folder-icon) when a folder is selected.

[Mingun]

If implement, I think, this feature should be configurable.

[goran-w]

If implement, I think, this feature should be configurable.

Which part(s) of it? Showing 'something' instead of just an empty page won't need to be optional, I think? Presumably it's the special-case for single-file-content you want to optionally preserve? (And if so, why would it be preferable to the more consistent behavior of always displaying exactly what's selected?)

[Mingun]

Checkbox with the meaning "Show file content when there is only one file in a folder when folder is selected"

[goran-w]

Checkbox with the meaning "Show file content when there is only one file in a folder when folder is selected"

Right. When/why would this be preferable, then? (I mean the feature itself, not the checkbox. I'm just curious, since I don't really see the point - I rather find it confusing, as it doesn't match my selection and when I navigate down into the folder there's no change in the content shown... Also, a single-file-folder is a relatively rare special-case and this feature breaks the expected behavioral pattern.)

[Mingun]

If it exists, it was add for purpose, I believe. Therefore, it is probably better to leave the setting -- someone needed it.

[love-linger]

If it exists, it was add for purpose, I believe. Therefore, it is probably better to leave the setting -- someone needed it.

Uh… I just didn't address this issue out of sheer laziness. On the FILES page, content is loaded layer‑by‑layer (meaning SourceGit only runs the git ls-tree -- <folder> command on expanded directory nodes to generate child nodes, so as to avoid performance and resource consumption issues caused by loading the entire file tree at once when the repository is overly large), hence this problem does not occur there.

[love-linger]

Done.