Shields: Show full star count

Created on 24 May 2017  路  8Comments  路  Source: badges/shields

It'd be awesome to have an option to show the full star count rather than the abbreviated version, i.e. rather than showing "Stars 7k" I want to see "Stars 7,278". :blush:

screen shot 2017-05-24 at 12 24 41

Love this service, thanks so much for making this a thing!

question

Most helpful comment

IMO badges should be able to display a decimal if they are < 10 eg: 1.2k 2.5k 11k 120k,
As there is quite a big difference between 1k and 1.4k where as not such a big difference between 12k and 13k in terms of percentage.
For example I have a chrome extension which i use the badge for, and it all of a sudden jumped from 1k to 2k which looked a bit strange, I also don't get to see it slowly progress, only get to see the major jumps (unless i goto the dashboard)

But i agree it does not look as consistent which is a primary goal of the project.




All 8 comments

Hi, thanks for your suggestion. The full count makes the badges a bit messier, so I'd tend to argue for leaving them as they are.

Hi, @paulmelnikow
Honestly, I also want the feature. It should depends how customer wants to see it.

I prefer 5.21K or 2.45M (2 digit after point).

_Just a suggestion:_ As we can change the label of badge using optional parameter, it will be better if it can be customize using optional parameters (eg.?dataFormat=) and as there has a standard function metric(), if we pass the data object in the metric() function as an optional parameter and the metric() will return the value according to data.dataFormat.

This request is for https://github.com/mingrammer/go-web-framework-stars. If the Shields badge designs were integrated into that page, how would it look?

The more I look at it, the more I'm not convinced that for projects with a lot of forks, 12517, 12136 is more helpful or legible than 12.5k, 12.1k.

It should depends how customer wants to see it.

The project owner is a customer, but so is a visitor who is looking at the readme. Providing the visitor a consistent experience across projects is also part of our goal of providing consistent, readable badges.

I got your point (y) :)

IMO badges should be able to display a decimal if they are < 10 eg: 1.2k 2.5k 11k 120k,
As there is quite a big difference between 1k and 1.4k where as not such a big difference between 12k and 13k in terms of percentage.
For example I have a chrome extension which i use the badge for, and it all of a sudden jumped from 1k to 2k which looked a bit strange, I also don't get to see it slowly progress, only get to see the major jumps (unless i goto the dashboard)

But i agree it does not look as consistent which is a primary goal of the project.




My question is still this:

This request is for https://github.com/mingrammer/go-web-framework-stars. If the Shields badge designs were integrated into that page, how would it look?

If anyone would like to mock something up (using static badges, say), I'd be happy to consider it.

This is one of the most important aspects of starring to see a more accurate count rather than something rounded up by as much as 200 votes, a project with 2.800 stars is seen as 3K, I would say thats neither accurate nor realistic.

Please stop rounding things up. Else may as well just invent a star count and make a full static image badge, so that way I may show visitors I have 99999 stars when in hypothetically have 99. I would also be rounding things up by any arbitrary number not defined by some faulty logic other than my own.

If anyone would like to mock something up (using static badges, say), I'd be happy to consider it.

I dont understand the issue. see


Star

vs

GitHub stars

both live badges except using http://github-svg-buttons.herokuapp.com the design choices are limited which is just not ideal, but at least star counts are accurate and not made up.

Hi all, we understand you may be disappointed that Shields is not offering this feature. However we are offing a workaround: the Endpoint badge. You can use it with tools like RunKit and Jupyter Kernel Gateway to implement the exact badge content and logic you want, while letting Shields take care of formatting, rendering, and caching.

If you decide to use the new feature, your feedback is much appreciated! Please feel free to comment on the Endpoint beta issue if you have feedback or questions about how to use it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

korenyoni picture korenyoni  路  3Comments

kerolloz picture kerolloz  路  3Comments

techtonik picture techtonik  路  3Comments

stclairdaniel picture stclairdaniel  路  3Comments

PyvesB picture PyvesB  路  3Comments