Ok so I was talking to my computer science teacher earlier and he said that he would rather use vim over PHPStorm for creating a laravel project. WTF!

Normally I would be cool with it, but he has pushed faulty code to git over 8 times. I'm just done.

Guess a pre commit hook that runs the tests would be useful.

Get your unit tests and syntax checking attached to pre commit hooks as @lotd said. will save everyone a headache and will prevent committing if the tests fail (if set up right),

i have no issue with using an editor without syntax checking features but don't let that be an excuse to commit poor code.

there's nothing wrong with using vim cause with the right plugins it can do everything phpstorm or any other ide can, sounds like the guy either doesn't have good plugins (I know mine bitch loudly when I fuck up) or don't know shit about best practices. or maybe both

@PerfectAsshole @C0D4 don't get me wrong, I main vim for certain projects but what triggers me is not that. Its that he pushed faulty code then blames it on vim.

Like learn something new. My gawd

@n3xus wow, he's lucky I'm not in his class cause I'd make an ass out of him quick

@PerfectAsshole I already do a lot. I got stuck with him to overview the project and help because my app is handling confidential student information.

@n3xus
I use vim at times myself, I have nothing against it.

I was only suggesting using pre-commit hooks so when that person goes to make a commit, whether he is using an IDE or not, the code checking is already done. And will prevent a commit occurring in the first place if something is wrong, like a syntax issue on a file, or a unit test fails.

You could probably roll this out as team thing, to try an improve the quality of code of all project members rather then single out a single member.

@C0D4 alright. Thanks for your help.