Maven central version badge should not be prefixed with 'v'

[onacit]

Are you experiencing an issue with...

shields.io

🐞 Description

I seems the Maven Central Version seems prefix v. I don't have any clue for any purpose or intention.

e.g.

The v doesn't add any value but some confusion.

🔗 Link to the badge

No response

💡 Possible Solution

Remove the v prefix from the version value.

[jNullj]

Shields.io employs the renderVersionBadge function to render versions consistently across the project (horizontal consistency), including maven-central, by always adding the v prefix using addv.

We have several options to consider:

1. Change only maven-central to remove the prefix, which would break horizontal consistency and create inconsistency among shields.
2. Remove the prefix in all version renders, improving vertical consistency for this badge.
3. Add an option for users to customize the prefix.

A comprehensive discussion on this topic is already underway in issue #10437.

IMO option 3 is best while i think the default should stay with the prefix for now until a standard is set.
Let us know what you think and what solutions you had in mind.

[onacit]

@jNullj Thank you for the comment. I'm not going to go deep into the issue you mentioned. I agree. Adding an option for users to customize the prefix will help.

[ryan-williams]

+1, this isn't specific to Maven Central badges, I'd like to omit the "v" for PyPI and NPM badges as well. It adds no info, and wastes precious horizontal space on mobile.

Obvious solution:

• messagePrefix query param, defaults to "v"
• ?messagePrefix=&… would make it the empty string.

Strange to hard-code the "v" prefix and give no option for overriding.

#10437 seems to be much broader / not obviously related.

[calebcartwright]

For historical context I'll also point back to #6135

but regarding 👇

#10437 seems to be much broader / not obviously related.

#10437 is directly related, the standardized v prefix on version badges was discussed there explicitly and at length

e.g.

#10437 (comment)

Some examples that come to mind of cases where we've opted for horizontal consistency over vertical consistency are things like where we add prefixes/suffixes (e.g. v on version badges), code coverage using different levels of precision (e.g. 92.51% vs 93%), download counts, and pipeline status wording

#10437 (comment)

Yeah all good examples - thanks.

I feel like always adding v on version badges and decimal precision/rounding are stylistic/presentation concerns. They don't change the meaning of the value.

etc.

Probably best to read things or at least ask for more direct pointers to related information before pushing back and characterizing something as unrelated