Open Kaympe20 opened 2 months ago
@sciencewhiz A VSIX file is already made. Why wouldn't that newer VSIX file be uploaded to the vscode marketplace?
We want teams to use the installer. It really helps ensure that teams have a consistent experience and makes our lives exponentially easier when teams come to us with issues.
Some use cases, such as devcontainers/codespaces, cannot be automated to their usual extent without it being in the repos. Additionally, the installer has a plethora of issues including that you cannot sign into GitHub on Linux.
For Java projects, theres nothing the WPILib extension actually does for devcontainers and codespaces. Since deployment doesn't work, and thats basically all those extensions add.
As for the GitHub issue, that will be fixed in 2025 with new VS Code versions. Or you can manually trigger an update of the installed VS Code.
For people that do want to install into an unsupported setup, the VSIX can be manually installed into any copy of VS Code. Theres nothing special in the WPILib VS Code, its just a fixed version.
@ThadHouse GitHub Codespaces is extremely useful for school settings as it allows you to create a development environment in the cloud. WPILib's vscode extension has tons of useful features for developing the robot's code, even to those that cannot be the ones to upload the code to your robot. Some of these include the library management functions, class create, and even project creation. Why would you limit the students that can code only to those that have laptops that can install software?
Additionally, the installer has a plethora of issues including that you cannot sign into GitHub on Linux.
Can you open issues for those things?
@sciencewhiz As @ThadHouse stated, that is just a byproduct of the included version of vscode just being very old.
You said the installer had a plethora of issues and then named one. Please create issues for the others.
Additionally, please create an issue for the GitHub Linux issue. Thad is right that it will be fixed for next years release. But we can't document known issues or workarounds for things we don't know about.
Per the VSCode marketplace message: