-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
introduce a fully featured version manager #230
Conversation
@Vexu Any thoughts on these changes? |
I allowed myself to mention your PR here ! I can remove it from the list if you desire |
7c6cb52
to
1475806
Compare
I'm guessing there is precedence for extensions downloading additional binaries unprompted when installed so I guess that is fine especially since it is from the official source. As long as overriding the path to the Zig binary still works these all seem like good changes. And sorry for taking so long to get to this. |
1475806
to
528a402
Compare
528a402
to
64753bd
Compare
e0e9efb
to
a59bc53
Compare
These changes make ZLS an "invisible" component of the extension after the initial setup. This also removes the `zig.zls.checkForUpdate` command. I am not sure if it even needs to be brought back. I've made sure that no error is reported if no internet connection is available. The last installed ZLS version should be reused. closes #136 because `zig.zls.startRestart` will just enable ZLS instead of complaining
The manual update command is already covered by the 'Select and Install' popup.
This commit replaces the initial setup with the following mechanism: 1. Check if the "Install Zig" has been previously executed in the active workspace. If so, install that version. 2. If the workspace contains a `.zigversion`, install the given Zig version. 3. If the workspace contains a `build.zig.zon` with a `minimum_zig_version`, install the next available Zig version. 4. Otherwise fallback to the latest tagged release of Zig. Some parts of this are not fully implemented. fixes #111
- add the ability to remove the workspace zig-version - add an option to manually specify the path to Zig - add an option to select Zig from PATH (if available) - display the exact version of nightly - display which versions are already installed on the host machine - make the popup usable without an internet connection
This unfortunately has a large impact on the bundle size: 600kb -> 1.3mb
For now, the list of mirrors has been manually copied over from mlugg/setup-zig. Adding mirrors for ZLS is also possible even though none exist. fixes #238
It is expected to be removed in ZLS 0.14.0
a59bc53
to
b6adadc
Compare
b6adadc
to
d5430e3
Compare
Ready for Review 🚀 Also, I think that publishing a pre-release can make sense here. I can ask in some of the Zig communities to see if there are people who would like to try this out before it gets published to everyone. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I published this as 0.5.10 (pre-release)
so you can get people to try it after which I'll release it as 0.6.0
.
How about the following changes:
The result would be |
- removed redundant "Zig" from text - changed the Name (that appears in the context menu) from "Zig" to "Zig Version"
You are referring to the status bar items, right? The reason why I had it this way was because they were made up of two independent items, the |
A similar test is already done in versionManager.ts
This should help when going back to the extension version. Otherwise it wont show the initial setup popup again.
This also fixes some cases where the status item would incorrectly state that ZLS is running
I did find some minor issues that have been resolved. Otherwise, this is ready to go. I can open some new issues about the follow-up tasks. |
Installing Zig or ZLS with the extension doesn't properly handle switching between different Zig project.
You have to manually figure out which version to get and install it every time your switch to a project that requires a different Zig version. Same goes for ZLS. The vscode configuration for Zig also can't handle switching between devices (see #111)
Let's stop giving developer the ability to misconfigure their editor.
Version Manager
This is how the extension selects which version of Zig to install:
zig.version
config option (can be global or per-workspace)minimum_zig_version
in thebuild.zig
of your workspace.zigversion
to your workspace which stores the desired Zig versionIf none of the above apply, the latest tagged release of Zig is installed.
Installs are automatically uninstalled to not fill up disk storage too much.
Installs are downloaded from mirrors just like setup-zig (fixes #238) and verified with minisign
The version of ZLS is inferred from the Zig version.
One unfortunate limitation is that the Zig installation will fail if the exact Zig version in the
build.zig.zon
is not provided as a prebuilt binary. There is no mechanism in place that will try to find the next available version.Status Bar
Hovering over the "Editor Language Status" will show whether Zig and ZLS are installed + their versions. The Status Bar Item for Zig will turn red if is not installed. Clicking on it will open the 'Select and Install' popup.
Updated 'Select and Install' popup
Zig version update
zig.update
command has been removed. The 'Select and Install' popup can be used instead.zig.checkForUpdate
has been removed. I can open a follow-up issue about it. I can foresee this needing some extra discussion to evaluate whether this feature is worth bringing back and how exactly it should behave.follow-up tasks
.zigversion
orbuild.zig.zon
.zigversion
orbuild.zig.zon
minimum_zig_version
I wanted to keep these changes as small as possible but I couldn't stop myself. 😞
Any feedback would be greatly appreciated.