That's a very good question. I think it should be per Che workspace (careful not to mix the term with VSCode workspaces). VSCode plugins will make the assumption that they run on a single machine. That implies that when they address a file system path, they are addressing the same file or folder. This is not the case when we have two different Che workspaces: "/projects/project1" could mean two completely different projects. So when we have per file metadata, for example, a vscode plugin would key that metadata by the file's path, so we need separate storage locations for each Che workspace. Does that make sense?
/Thomas
On Fri, 2018-12-14 at 08:07 -0500, Gorkem Ercan wrote: Is this per workspace or per user data ? Hello.
I am working on implementing some plugin context API in Theia. The plugin context API specification requires some data of plugin to be persistent, so we need to save it on workspace stop and restore on workspace start. Many plugins use this functionality to store data of many kinds, including sensitive data. For example, Github plugin stores Github token there.
I want to use a volume in Theia sidecar to reach that. Does anyone has any concerns about this approach?
|
