-
-
Notifications
You must be signed in to change notification settings - Fork 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
allow setting patches file location through --patches-file
option (fixes #25)
#26
Conversation
I'm not really sure what the issue with rector is, it wasn't working for me locally even before I made any changes either. If that's something I did wrong, please let me know. |
Rector in composer.json still on 0.18.3 Line 20 in 585e750
Could you try upgrade to ^1.2.5 ? Thank you. |
7c56344
to
2907192
Compare
Please don't merge, I just noticed there's a bug. I'll fix it in a couple of hours when I back. |
Fixes have been applied, sorry for the delay. Let me know if there's anything else missing. |
@TomasVotruba is anything missing for this to be merged? |
All good. Could you update the readme as well? |
Done |
Thank you 😊 |
Adds
--patches-file
option which allows using a patches file instead of relying oncomposer.json
.Since the structure for the
patches.json
is "shallower" (noextra
at the top) the code path is a bit different. Could have done a slightly bigger refactor, but I like to try and keep things simple when contributing to someone else's code.When
--patches-file
is set we assume this shallower format, meaning you can't call with--patches-file=composer.json
. Could instead check the file name at runtime and decide what format to use, but this was simpler and I think it makes sense. Let me know what you think.Also add a test for changes.