Replies: 1 comment 4 replies
-
Hmm. I'm seeing the same problem as you, but I don't know what's causing it. |
Beta Was this translation helpful? Give feedback.
-
Hmm. I'm seeing the same problem as you, but I don't know what's causing it. |
Beta Was this translation helpful? Give feedback.
-
Hello! Thanks for the Shields service, long time user, first time / recent developer of custom badges.
I've built a very simple JSON server to power some custom badges -> https://twbadges.glitch.me/
As of today, I'm seeing inconsistent behaviour for the badges. Sometimes, some of them, show up with a grey badge stating "custom badge | invalid".
I'm trying to track down the best way to debug this. So far as I can see, when I reload the page, the number of calls from shields.io back to the server is itself inconsistent, resulting in the "dropped" badges. For example, when I reloaded the page just now, I saw 5 hits on the JSON backend, corresponding to 5 correctly-rendered badges; and two that show as invalid.
So, my assumption is that there's a bottleneck on the Shields side itself. Clearly this particular page is a showcase / demo rather than the way I expect the badges themselves to be used; I'd imagine one, two, at most three, might be added to a single README file; so I don't expect the kind of constant reloading I'm causing as I test the front-end web page.
I suppose I could build an "API version picker" for a developer to select the badge they want and render them individually on-demand, which might be better practice / better performance / a way to be a nicer citizen to Shields?
Any thoughts on the behaviour I'm seeing would be appreciated :-) thank you!
Beta Was this translation helpful? Give feedback.
All reactions