Stop prepending "Maven Central" versions with "v"

[cstamas]

Are you experiencing an issue with...

shields.io

🐞 Description

It is misleading, as there are artifacts that have versions like "v1.2.3" (version starts with letter "v"), so shield would show "vv1.2.3".
Just leave the blue field "as is" (verbatim as version is).

🔗 Link to the badge

https://img.shields.io/maven-central/v/org.apache.maven.resolver/maven-resolver.svg?label=Maven%20Central)](https://search.maven.org/artifact/org.apache.maven.resolver/maven-resolver

💡 Possible Solution

Just drop the prepended "v" from version in blue field.

[github-actions]

Badge tested using npm run badge https://img.shields.io/maven-central/v/org.apache.maven.resolver/maven-resolver.svg?label=Maven%20Central)](https://search.maven.org/artifact/org.apache.maven.resolver/maven-resolver
Output is available here

[kwin]

The prefix v is already conditional. See

shields/services/version.js

Line 259 in 1809d1e

(prefix ? `${prefix}${version}` : addv(version)) +

and

shields/services/text-formatters.js

Line 134 in 1809d1e

function addv(version) {

.

[cstamas]

Whatever, by by default the version should not be "v" prefixed. This is wrong, and actually the opposite that should be: If I want "v" prefix, I'd need to turn something ON, and not turn OFF to lose some prefix being automatically added.

[michael-o]

Whatever, by by default the version should not be "v" prefixed. This is wrong, and actually the opposite that should be: If I want "v" prefix, I'd need to turn something ON, and not turn OFF to lose some prefix being automatically added.

Agree, it has not benefit or purpose because it constantly repeats.