-
Notifications
You must be signed in to change notification settings - Fork 5
Work for satisfy recent Composer versions and a couple of features #15
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
base: master
Are you sure you want to change the base?
Conversation
…Interface only defines a sub-set of operations needed by neronmoon/scriptsdev and RootAliasPackage only implemented those methods defined by the interface. Most of the unimplemented methods in RootAliasPackage can be worked around because the getter methods that are implemented proxy to the aliased package which we can modify by unwrapping.
- Bugfix to skip warning about previous commands existence. - Read/writes JSON composer way (adopted from `composer/satis`) - Some refactor and minor improvements. * Features to be tested: - Remove duplicates by `scripts-dev-replace` key (adopted from `wikimedia/composer-merge-plugin`). - Remote merging by `scripts-dev-remote` (adopted from `composer/satis`, theoretically have precedence `scripts-dev` versus `scripts-dev-remote`, and theoretically only works when `scripts-dev` is missing while `scripts-dev-remote` no)
Strange behaviour with `legacy-with-run-scripts-dev` test: ---------------------------------------------------- legacy-with-run-scripts-dev [['composer', 'update'], ['composer', '--no-dev', 'run-script', 'test']] ---------------------- outputs --------------------- Exception: EXPECTED "SCRIPTSDEV RULEZ" BUT FOUND "SCRIPTSDEV RULEZ" -------------------
…th builtin composer + symlinking path, and makes running tests ultra-fast.
With the gone previous behaviour another wrong one comes out, this time with `extra-with-custom-script-run-script-dev` test: ---------------------------------------------------- Testing: extra-with-custom-script-run-script-dev [['composer', 'update'], ['composer', 'test']] ---------------------- outputs --------------------- Exception: EXPECTED "SCRIPTSDEV RULEZ" BUT FOUND "" ------------------------------͌ I seems its working with `post-install-cmd` or `post-update-cmd` commands but with the `test` command? Maybe Seldaek@599ad77167bc8cee895f024a20292689fd84153f can help somehow?
Added static analysis tool. Needs more tests.
Added static analysis tool. Needs more tests.
Added static analysis tool. Needs more tests.
Thank you for your work! Thank you |
Hello @neronmoon. I know have added some geeky dependencies, there are some fancy messages too, have a workaround with all current tests ok and will remove those unnecessary user-dependencies, but there are some "generification" in code that don't know if you like it. Wants ready to merge/replace any section almost in same way that did before (plus remote support), but doing just for scripts if no extends. You are welcome. Kind regards. |
In Composer versions before composer/composer@599ad77 the RootPackageInterface only defines a sub-set of operations needed by neronmoon/scriptsdev and RootAliasPackage only implemented those methods defined by the interface. Most of the unimplemented methods in RootAliasPackage can be worked around because the getter methods that are implemented proxy to the aliased package which we can modify by unwrapping.