-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Packages don't always have a source/reference #12
Comments
Ocramius
added a commit
that referenced
this issue
Feb 18, 2016
Ocramius
added a commit
that referenced
this issue
Feb 18, 2016
Ocramius
added a commit
that referenced
this issue
Feb 18, 2016
Ocramius
added a commit
that referenced
this issue
Feb 18, 2016
Ocramius
added a commit
that referenced
this issue
Feb 24, 2016
…-package-version-references Fix #12 - support dist and missing package version references
yay ! Do you mind tagging a new version (in the 1.x branch)? |
@magnetik yarp, gonna happen now. |
@magnetik released |
Awesome, thanks ! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Moved from Ocramius/ProxyManager#294
Basically, when using something like following:
As you can see, this package has no
source
reference, as it comes from a repository (in-lined in thecomposer.json
) that has no such information. Therefore, this call fails, causing a general failure of the code generation in the script.The text was updated successfully, but these errors were encountered: