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

Using dev-master is always bad #79

Merged
merged 1 commit into from
Dec 20, 2014
Merged

Using dev-master is always bad #79

merged 1 commit into from
Dec 20, 2014

Conversation

GrahamCampbell
Copy link
Contributor

No description provided.

jbrooksuk added a commit that referenced this pull request Dec 20, 2014
Using dev-master is always bad
@jbrooksuk jbrooksuk merged commit 7d5dc24 into cachethq:master Dec 20, 2014
@jbrooksuk
Copy link
Member

Thanks buddy.

@GrahamCampbell GrahamCampbell deleted the patch-1 branch December 20, 2014 20:41
@GrahamCampbell
Copy link
Contributor Author

np. :) Sorry I couldn't update the lock file again. This was a quick pull from github's online interface.

@jbrooksuk
Copy link
Member

Don't worry about it, I'm just about to push that.

@GrahamCampbell
Copy link
Contributor Author

Also, your description in the composer.json is incorrect. It says that this is laravel. :)

@jbrooksuk
Copy link
Member

Whoops! I'll change that now, good spot! :)

@GrahamCampbell
Copy link
Contributor Author

It would be cool if you published this to packagist too, so people can use composer create-project to install cachet.

@jbrooksuk
Copy link
Member

That's something I need to add to the roadmap actually.

I'm not sure if I should do that now or once v1 is released, what do you think?

@GrahamCampbell
Copy link
Contributor Author

I would. It does no harm. I did with bootstrap cms over a year ago, and I still haven't tagged 1.0 yet.

@jbrooksuk
Copy link
Member

Ok, awesome, I'll get on that.

@GrahamCampbell
Copy link
Contributor Author

👍

@jbrooksuk
Copy link
Member

Done.

@GrahamCampbell
Copy link
Contributor Author

👍

@GrahamCampbell
Copy link
Contributor Author

@GrahamCampbell
Copy link
Contributor Author

Interesting - your namespace violates psr-0/psr-4.

@GrahamCampbell
Copy link
Contributor Author

CachetHQ should be CachetHq apparently?

@jbrooksuk
Copy link
Member

Woah, cheers. That's interesting, I didn't know you couldn't have HQ.

I guess we could change it, but it does seem weird?

@GrahamCampbell
Copy link
Contributor Author

Yeh, it is odd.

@GrahamCampbell
Copy link
Contributor Author

#80

@GrahamCampbell
Copy link
Contributor Author

I can disable psr0 fixer if required, because it is odd. Maybe just namespacing it under Cachet would be a good idea?

@jbrooksuk
Copy link
Member

Thanks!

If we went with just Cachet it would be Cachet\Cachet and that feels odd to me. Especially since in the future we may develop custom packages under the CachetHQ org, I felt it should match the GitHub org too.

Is it PSR-0 that's causing the issue here?

@GrahamCampbell
Copy link
Contributor Author

No - it because you named the folder wrong...

@GrahamCampbell
Copy link
Contributor Author

It was adjusting the namespace because on case sensitivity matters on some systems for autoloading.

@jbrooksuk
Copy link
Member

Oh because it's CachetHq but the org is CachetHQ?

@GrahamCampbell
Copy link
Contributor Author

Yeh, the folder can't be named CachetHq when the namespace is CachetHQ. They must match.

@jbrooksuk
Copy link
Member

That's easy to fix :)

@GrahamCampbell
Copy link
Contributor Author

btw, I'm using /~https://github.com/FriendsOfPHP/PHP-CS-Fixer under the hood here.

The power to fix docblocks should be massively improving after PHP-CS-Fixer/PHP-CS-Fixer#887 goes through.

@jbrooksuk
Copy link
Member

That's awesome!

Blows out the need for @anorakci ;)

@GrahamCampbell GrahamCampbell modified the milestone: V0.1.0 Alpha Jul 25, 2015
@raffus raffus mentioned this pull request Mar 22, 2018
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.

2 participants