[plug-in] Ability to get current selection in the explorer view

[RomanNikitenko]

The use case where I want to use it for Task plugin is resolving the variables for Che tasks.
For example, we have command mvn clean install -f ${current.project.path} and we need to resolve it before running. So we need to replace current.project.path to execute the task for current project.

[tsmaeder]

@RomanNikitenko is this about implementing some vscode API call?

[RomanNikitenko]

@tsmaeder I'm sorry - I missed your message.
As far as I know vscode doesn't contain corresponding API.
So we need to find some way to get current selection in the explorer view on plugin side.

[vzhukovs]

As I understand, we need macros mechanism in general and macro for current project path is particular type of macro as an example.

[RomanNikitenko]

@vzhukovskii we have ability to register variable from plugin side. But I don't know the way how to get current selection in the explorer view on plugin side. We could resolve the variables for Che tasks replacing current.project.path by path of current selection

[vzhukovs]

For resolving actual variable ${current.project.path} we need to implement interface variable.ts#L24 on the plugin side and add additional method to obtain current selected paths (in theia.d.ts) which can be retrieved from selection-service.ts#L27

[RomanNikitenko]

@vzhukovskii we don't have problem with registration variable, so we don't need to implement interface variable.ts#L24, we can just register variable.
The problem is - we can not obtain current selected path on plugin side