This repository has been archived by the owner on Nov 4, 2023. It is now read-only.
Adds deprecation notice to extension title. #485
Merged
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hey there 😉
Thanks for putting the deprecation notice in your readme and for implementing the notification to prompt users to migrate to the native feature!
However, we still notice that many users install your extension.
Unfortunately, the VS Code marketplace has no mechanism of properly deprecating an extension yet.
Thus, we recommend to prepend the extension title with
[Deprecation], so that even though your extension appears in the list of the most popular extensions, users can see immediately that it is deprecated.I prepared this PR to help you with this, but we also understand if you like to keep your current extension name without the deprecation notice.
Thanks!