fix: restore handling of zipfile: schema for neovim + yarn berry #862
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
size-limit report 📦
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During earlier refactoring the
zipfile:schema override handling for neovim+yarn pnp has been broken. Those changes should restore proper functioning.Using the
URIclass to parse zipfile: URIs back and forth doesn't preserve triple slashes after the schema which yarn SDK expects to be there for neovim handling.Introduced a subclass of
URI-ZipfileURI- that persists the original URI and returns it fromtoString()so that yarn and neovim get what they expect.Resolves #843