franzliedke / studio

A workbench for developing Composer packages.
MIT License
1.14k stars 73 forks source link

Symlink not being created, wildcard not working #74

Open timersys opened 7 years ago

timersys commented 7 years ago

Issue 1: Wildcard load I got two packages on ~/Packages so I tried the following: studio load ~/Packages/* but I got the following error:

studio load ~/Packages/*                                                       
  [Symfony\Component\Console\Exception\RuntimeException]  
  Too many arguments.                                                                                            
load <path>

Issue 2: Symlink problem with package B I got 1 project type wordpress-plugin that requires 2 libraries in composer.json . so WP requires A and B

{
  "name" : "timersys/WP",
  "type" : "wordpress-plugin",
"require": {
        "timersys/A": "dev-master",
        "timersys/B": "dev-master"
    }
}

A library in composer.json also requires project B

{
  "name" : "timersys/A",
"require": {
        "timersys/B": "dev-master"
    }
}

Issue is that library B symlink is not being created and keep getting downloaded. I tried studio load also inside B but that makes not difference. Not sure what Im doing wrong but I can't make it work.

timersys commented 7 years ago

I tried with studio version from #73 and it worked both libraries are symlinked now. Problem A with wilcard persist

emri99 commented 7 years ago

Hmm may I ask if you tried to put quotes around ? :blush:

studio load "~/packages/*"
ElfSundae commented 7 years ago

Same here. macOS Sierra with Studio c1359ff9fdec24ca4e3ceb5dd38e09ce9ba8b2db installed.

ElfSundae commented 7 years ago

Fixed by adding all local packages as dev-master version to my app's composer.json file.

Before:

A -> app
B -> A

=> Now:

A:dev-master, B:dev-master -> app
B -> A

and

studio load "/data/projects/php-packages/*"