Thomas Mäder
Thomas Mäder
### Bug Description: On Windows, I can open a workspace folder by doing `theia.exe ### Steps to Reproduce: 1. Make sure Theia is not running 2. Run `~\AppData\Local\Programs\Theia\Theia.exe ### Additional...
### Feature Description: The VS Code installer offers the option to add the "code" executable to the shell path. I'd like that too, in order to just use `theia .`...
### Bug Description: When installing the Theia IDE on Windows/latest, the user is asked to accept the MIT license. This is not correct, since most of the code in Theia...
This generator generates a whole Theia-based application, not just a Theia extension, yet it's is invoked with `yo theia-extension`. A naive user will be surprised.
We have one yeoman generator that is invoked with `yo @theia/plugin` and this one is invoked with `yo theia-extension`. Why not use the same syntax like `yo @theia/extension`?
We currently generate various things like "Hello World", etc. Why not have a single generator that can generate Theia plugins as well? Like ``` yo theia -y plugin ```
Other generators (like `yo @theia/plugin`) create a directory that contains all their artifacts. This generator generates a bunch of artifacts inside the current directory.
I have a package.json with multiple workspaces in them, having for example a package at `sample-plugins/sample-namespace/sample-plugin` (see below). I do an `npm install`, producing a package-lock.json. When I run dash-licenses...
### Feature Description: LLM's often take considerable time generating answers. In that time, the user often does something else. It would be nice if there was an unobtrusive notification when...
- use webUtils.getPathForFile() in drag and drop - upated supported node versions to v20-v24 Fixes #15672 #### What it does #### How to test Test general use of Theia, with...