feat(extensions.json): Boundary.baml-extension-preview should redirect to Boundary.baml-extension #810
Conversation
This file contains 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
filiptronicek
approved these changes
Jan 20, 2025
There was a problem hiding this comment.
Hi there @sxlijin, and thanks for your contribution! The PR looks good and if you sign the Eclipse contributor agreement (link should be in the PR checks below), we should be good to go.
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.
Per docs, I'm requesting a deprecation of https://open-vsx.org/extension/Boundary/baml-extension-preview.
Boundary.baml-extension-preview was published while doing some internal alpha testing of our open vsx release process, but because I chose such a similar name to our actual extension, Boundary.baml-extension, it looks like some of our users have landed on baml-extension-preview instead of baml-extension.
Deprecation seems like the correct way to handle this; please let me know if there's a more appropriate way to do so.