Conversation

andyleejordan

As it took a year (presumably, maybe a more recent VS Code update is what broke it) to come up that indicates its usage is too low for us to go about fixing. If someone wants to figure it out we'll be happy to take a PR. For now we're removing the code (which is also a massive simplification because it was the entirety of the "VSCode" module we had to build and ship with the extension).

As it took a year (presumably, maybe a more recent VS Code update is
what broke it) to come up that indicates its usage is too low for us to
go about fixing. If someone wants to figure it out we'll be happy to
take a PR. For now we're removing the code (which is also a massive
simplification because it was the entirety of the "VSCode" module we had
to build and ship with the extension).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Glad that we can decide to cut features that are not used enough!

@andyleejordanandyleejordan added this pull request to the merge queue Jan 25, 2024
@andyleejordan

Me too! Goal is to reduce the surface area we have to maintain. I want a stable, quality extension even if it's smaller! Not an extension trying to implement everything possible under the sun but failing at all the core features.

Sign up for free to join this conversation on . Already have an account? Sign in to comment
Area-Engine Issue-EnhancementA feature request (enhancement).
Status: Done

Successfully merging this pull request may close these issues.