This way is fine, once you've already got the module set up to be required from composer.json
It can start out in ./module until is ready to be committed on its own and included. Then once it is set up, composing it in and working on it in ./vendor works fine. I've also created a separate local project for the module and added that path to the psr-0 section of my main project composer.json instead of adding it to the require section. This easy it doesn't get installed in your project at all, but it does get added to your class map. Jeremiah > On Oct 3, 2014, at 5:23 AM, Brian Gallagher <[email protected]> wrote: > > Hi All, > > I'm wondering what approach people are taking to develop modules which are > handled by composer? > > Currently I'm adding my module & repo (private bitbucket) to my root > composer file, I then update composer which pulls in my module, then I work > on my module within the vendor folder, commit, push , and repeat. > > But it seems odd to be working within the vendor folder. Just wondering how > other people manage their module development? > > Brian -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
