Added Composer. See #11

GaryJones / Gamajo-Template-Loader

A class to copy into your WordPress plugin, to allow loading template parts with fallback through the child theme > parent theme > plugin.

GNU General Public License v2.0

292 stars 61 forks source link

Added Composer. See #11 #12

Closed Rarst closed 10 years ago

Rarst commented 10 years ago

library is default type, omitted
I didn't include second class into autoload since it seems to be for example only

GaryJones commented 10 years ago

Thanks!

Rarst commented 10 years ago

You are welcome. :) Don't forget to spend a minute and set up on https://packagist.org/ for easy installs.

GaryJones commented 10 years ago

All done and set to auto-update: https://packagist.org/packages/gamajo/template-loader

GaryJones commented 10 years ago

I can see that dev-develop is listed on the packagist. Does that mean if I update the develop branch here, and someone does a composer update, they'll immediately get a new version?

If so, I think I probably want that as dev-master, since I use git-flow, so only stuff on the master branch is considered release worthy. Is there a way to change composer.json to tell Packagist that?

Rarst commented 10 years ago

Getting dev branches with Composer is under Slightly Bad Ideas. Really as soon as you tag next version it will have composer.json and will show up as stable version on Packagist — which is what people should get in most cases.

dev-master will show up as well after you merge composer.json into it.

GaryJones commented 10 years ago

To be clear - I don't want dev branches available via Composer.

dev-master will show up as well after you merge composer.json into it.

Ah, of course, that's what I was forgetting. Thanks :-)

Rarst commented 10 years ago

Well, they are going to be since they are available via git. :) You don't prevent people from cloning develop, right. Composer infers the same with additional requirement of composer.json in branch.