Update editor tabbar captions for better multi-root support

[vince-fugnitto]

What it does

Fixes #5921

• updated the editor's caption (used for tabbars) in order
  to better support multi-root workspaces, and align with VSCode.
  Currently, when in a multi-root workspace there is no way to
  easily distinguish which root the file resides in. With this
  change the entire path is displayed, similarly to the explorer.

How to test

1. open a single-root workspace, open an editor, and highlight over the tabbar (the entire path should be displayed as the html title)
2. open a multi-root workspace, open an editor, and highlight over the tabbar (the entire path should be displayed as the html title)

Review checklist

• as an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• as a reviewer, I agree to behave in accordance with the review guidelines

Signed-off-by: Vincent Fugnitto vincent.fugnitto@ericsson.com

[vince-fugnitto]

@akosyakov I know the coding guidelines state to use the labelProvider.getLongName() in order to get a uniform representation of the path systemwide, but it does not work correctly for the following case.

Debugging the code I can see that WorkspaceUriLabelProviderContribution is used while I require the default implementation present in the DefaultUriLabelProviderContribution.

https://github.com/theia-ide/theia/blob/11badc80598254e8c78a204b7b93c2368a300fe4/packages/core/src/browser/label-provider.ts#L83-L86

Is there a way to be able to programmatically decide which contribution I want to handle the implementation of the method (ex: Default over Workspace)?

In order to get the correct results, I followed the logic present in the file-tree-widget.tsx:

https://github.com/theia-ide/theia/blob/11badc80598254e8c78a204b7b93c2368a300fe4/packages/filesystem/src/browser/file-tree/file-tree-widget.tsx#L96

[akosyakov]

but it breaks single root scenarios? Should not we work on improving getLongName for multi-roots?

Have you checked what VS Code show? I would imagine we can show something like README.md (cpp)?

[akosyakov]

ok, checked with VS Code, for tooltips always the full path is used

[vince-fugnitto]

ok, checked with VS Code, for tooltips always the full path is used

Sorry I just got to work, yes exactly, they display the long path irregardless of if its a single or multi-root workspace.