Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JS Standard #11

Merged
merged 3 commits into from
Mar 9, 2015
Merged

JS Standard #11

merged 3 commits into from
Mar 9, 2015

Conversation

mightyiam
Copy link
Contributor

Fulfills #10.

Hrm... Shields.io provides several styles (see "Styles" section).

Can we support that?

@mightyiam
Copy link
Contributor Author

@feross FYI

@jonschlinkert
Copy link
Member

thanks!

jonschlinkert added a commit that referenced this pull request Mar 9, 2015
@jonschlinkert jonschlinkert merged commit 8d83070 into verbose:master Mar 9, 2015
@jonschlinkert
Copy link
Member

oops, forgot to replace your username the templates. no worries I'll do that now

@jonschlinkert
Copy link
Member

nvm I don't think these need username, I'm reading over shields.io now

@mightyiam mightyiam deleted the patch-1 branch March 9, 2015 22:06
@mightyiam
Copy link
Contributor Author

Right, these don't have usernames.

@mightyiam
Copy link
Contributor Author

Thank you.

@jonschlinkert
Copy link
Member

got it, looks good, thanks!

@jonschlinkert
Copy link
Member

published 0.1.2, a patch bump since this just adds templates and doesn't break anything.

@mightyiam
Copy link
Contributor Author

published 0.1.2, a patch bump since this just adds templates and doesn't break anything.

Digressing here.

According to semver that should bump the minor version, because it is a feature.

The patch is for bug fixes.

@jonschlinkert
Copy link
Member

According to semver that should bump the minor version, because it is a feature.

Not really, it's not a new feature - more specifically it's not new "functionality", which is what semver specifies. Just new templates for the badge() helper to use. I can see how we could make a case that adding new templates would be "new functionality", but given that the templates themselves don't have any variables, there is nothing in them that can break this library or, when explicitly defined by a user, that could break the badge() helper. The badge helper does not need to change to leverage the helpers, and nothing was fixed either.

Anyway, moving away from semver philosophy, just being pragmatic, if we do a minor bump you wouldn't be able to use this until I bump this in verb and verb-cli then publish new versions of both.

@mightyiam
Copy link
Contributor Author

if we do a minor bump you wouldn't be able to use this until I bump this in verb and verb-cli then publish new versions of both.

I would imagine that verb and verb, for example, v0.1.1 should peerDepend on verb-readme-badges, v^0.1.1. In that case, bumping the MINOR shouldn't prevent verb from using verb-readme-badges.

Isn't it like this?

@jonschlinkert
Copy link
Member

Hmm, I might have used peerDepencies for the templates a while back. I'll look into it again. thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants