Skip to content
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

Reason why it only works with "dev-master"? #77

Closed
markvaneijk opened this issue Sep 6, 2017 · 2 comments
Closed

Reason why it only works with "dev-master"? #77

markvaneijk opened this issue Sep 6, 2017 · 2 comments

Comments

@markvaneijk
Copy link

I would like to know if there is a reason why "studio load" and then composer install/update only works when the composer.json requires the package as a "dev-master" version? I would like to specify the version with "*", so I don't need to change it every time I work on a package (and forget to change it back when commiting).

@rask
Copy link
Contributor

rask commented Sep 26, 2017

This is a known problem with a fix in the works if I remember correctly. After the fix lands you can create and load a local package with Studio without requiring any juggling inside composer.json (i.e. you should be able to keep the version constraint at "1.*" while your local Studio package is at "feature/my-feature").

The issue is that when you work on a local Studio package you need to redefine your composer.json to use the same tag/branch/ref which is checked out in the local Studio package at the moment.

Not sure about the exact reason why this juggling is required, have not dug that deep into the package code yet to know.

@franzliedke
Copy link
Owner

Indeed, this will be fixed with #52 / #73. Thanks for your patience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants