add templates support and new flat style option

[max-mapper]

this adds an option to all badges to do ?style=flat. you can now also easily add new styles if you wish to support more

[ghost]

👍

[espadrine]

Thanks a lot for implementing this! It is something that many vendors are interested in, looking forward.

This patch changes enough things that npm test fails. The failed assertions are caused by assumptions that the CLI program gh-badge.js makes. It is an easy fix: gh-badge.js requires colorscheme.json at an incorrect location.

We could also provide a way to specify which template to use in that program. Right now, we discriminate parameters using sigils (a . for the output format, a : for the colorscheme, a # for a hex color). We could use a dash, for once, I suppose. It wouldn't be as intuitive as the other sigils; suggestions welcome.

Maybe as a follow-up?

[max-mapper]

@espadrine ok should be good to go

[espadrine]

@maxogden This is good enough to merge. Thanks again!

I'll do some follow-up cleanup however before pushing to http://shields.io.

• The information stored in makeImage's options parameter is better served in its data parameter,
• The colorscheme parameter to makeTemplate is no longer used: I'll eat it,
• We can already get to the contents of the URL query parameter style through that data parameter in getRequest (in fact, the code setting the badge data is better located in getBadgeData),
• I'll adjust code style for consistency, esp. w.r.t. semicolons.

[espadrine]

It's live!

[max-mapper]

@espadrine w00t! I just noticed that the 'custom' badges ignore the ?style=flat, e.g. http://img.shields.io/badge/Made%20with%20freedom%20in-USA-blue.svg?style=flat

[espadrine]

@maxogden Hmm, that is rather unfortunate. I suspect it is caused by the fact that custom badges don't go through that cache. I shall have this fixed first thing tomorrow, UTC+2.