Open janhartigan opened 8 years ago
This is so useful! I really appriciate all the work Studio got in the past. But also for me, it is daily frustrating to clean up studio.json
before pushing. @franzliedke do you see any chance to make this a bit more comfortable?
This is so useful! I really appriciate all the work Studio got in the past. But also for me, it is daily frustrating to clean up
studio.json
before pushing. @franzliedke do you see any chance to make this a bit more comfortable?
I have my own composer-link https://github.com/SanderSander/composer-link which tries overcomes the issues.
@SanderSander I was just able to test your composer-link package and it is awesome! Thank you so much for the note. Now looking forward to have wildcard folder support. For everyone here who needs a simple and fast solution to link Composer packages from different paths, have a look at this.
We've been struggling with this as well and created a new Composer plugin https://github.com/ALDIDigitalServices/ComposerPackageDevelopmentToolset. Feedback appreciated.
Hey @franzliedke thanks a lot for taking the time to put together the recent release.
However, I have noticed one significant issue with the newly-generated
composer.lock
file. Normally composer generates something like this:There would also be a
dist
with the zipped contents of the git repo.With the new updates, the composer lock file now looks like this:
Trouble with this is that when we push the code up through the pipeline, our servers will try to install that
composer.lock
file and it won't be able to figure out how to grab the dist. Since you're already using this in a real project, I'm guessing there's some other approach that I'm missing. Let me know what you think.