docs(readme): fix broken vs marketplace badges#28
Merged
Conversation
Shields.io dropped support for vs marketplace badges in badges/shields#11792. This makes the badges render useless with the "retired badge" text instead. - Replaced the version badge with an Open VSX Registry version badge. - Replaced the installs badge with a static text badge to set an approximate number of vs marketplace installs based on the actual number.
96eb2fd to
28a545c
Compare
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
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.
Shields.io dropped support for VS Marketplace badges in badges/shields#11792. This makes the badges render useless with the "retired badge" text instead.
Replaced the version badge with an Open VSX Registry version badge.
Replaced the installs badge with a static text badge to set an approximate number (
~1.5k) of VS Marketplace installs based on the current total (1,401 at commit time). The usage of~is to ensure it's read as an approximate number, and not as an exact number. This is the only work around (currently) for the loss of the dynamic badge.