-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer::getComposerFilePath() must be of the type string, bool returned #246
Comments
Probably the cause of the issue #206 |
Actually, the composer.json file is first created by Composer itself at https://github.com/WsdlToPhp/PackageGenerator/blob/develop/src/File/Composer.php#L39-L55. Could you try adding a exit(); call after these lines and check if Composer succeeds to initiate the composer.json file? |
Oh well, you are right!
Feel free to close my bug report, since it works as expected in CLI mode. And thank you for your great work :) |
I'll improve the method anyway, thanks for your feedback. |
Hi,
after updating the package generator from version 3.3.4 to version 4.1.0, I've get following error when starting the generator in standalone mode:
My code is very similar to the README example:
Workaround:
When I manually create a
composer.json
file directly in the output dir, the generator works again (and the PHP files are correctly generated) but thecomposer.json
file isn't updated, thecomposer.lock
file isn't created and thevendor
directory isn't created.Expected:
The
composer.json
file, thecomposer.lock
file and thevendor
directory should automatically be created.The culprit is following code in
WsdlToPhp\PackageGenerator\File\Composer
, that expectscomposer.json
to exist, even in standalone mode:The text was updated successfully, but these errors were encountered: