[Flow] Opinions? Setting up PhpStorm projects
Jacob Floyd
cognifloyd at gmail.com
Fri Aug 16 23:18:18 CEST 2013
I see two ways (maybe there's more?) to set up PhpStorm projects.
1) I can create a PhpStorm project for each package, and then add all of the Flow packages and other dependencies as Includes.
* this is great because code completion works while the environment is focused on what I'm working with.
* Using PhpUnit from within PhpStorm is awkward at best this way. I've been working on setting up a distribution somewhere else
2) I can create a super PhpStorm project for a flow distribution that includes that package I'm working on.
* this means I need to exclude all of the dependencies folders so that search/refactor doesn't keep asking if I want to change the code in the other packages as well (No, PhpStorm, I don't want to rename anything in TYPO3.Flow. Stop asking).
* following Karsten's guides[1] for using PhpStorm/PhpUnit is more straightforward.
So, what do you prefer? Do you have a project per package (it looks like Flow has an .idea folder in the repo...?) or per distribution? If you do it per package, how do you use PhpUnit?
Thanks,
Jacob Floyd
[1] http://blog.k-fish.de/2011/12/setting-up-phpstorm-for-use-as-flow3.html
http://blog.k-fish.de/2011/12/setting-up-phpstorm-for-use-as-flow3_19.html
http://blog.k-fish.de/2012/11/menage-trois-typo3-flow-phpunit-composer.html
More information about the Flow
mailing list