Open tgaertner opened 6 months ago
What kind of error do you mentioned?
Can not reproduce this one. Probably it was a problem with an earlier composer version.
Calling ddev coposer:app
resulted in executing composer -d /some/path
which produces an error. Somthing like "-d is not a valid composer command". Using --working-dir
prevended this error.
Since this is obviously fixed in composer - we can close this issue.
We could still change the param for better readability.
replace -d with --working-dir= to prevent error and correctly display composer script list when called without param like 'ddev composer:app'