Level 75
Read this article how you can use your own fork
https://medium.com/swlh/using-your-own-forks-with-composer-699358db05d9
Mar 12, 2021
4
Level 4
How to handle waiting for a PR in third-party package repository?
What is a good way/How do you handle it when your project is using a third-party package. But this package has a small issue that needs to be fixed.
You created a PR, but what happens if it's not accepted, or just takes a while (days, weeks, months).
What is the best way to handle this?
Off the top of my head, I'd say use the fork you created for the PR. But then you'd also need to release it on packagist.
Is this the "usual" way to keep working until something is integrated into the "official" package? Or is there a better way?
Level 61
If I'm using a package I usually create class in my App directory for it and use it like a proxy to the package. If there is some bug I can fix it in the class that I've created in my App directory. If I switch away from that package I can just change that class in my App directory and continue in a matter of 2-3 hours.
Level 80
Just bad-mouth the company on Twitter 😄 They tend to respond faster if someone’s attacking their reputation…
In all seriousness, a fork is usually the best way. I’ve had to do this recently for a Mailchimp SDK and Cloudflare’s. Cloudflare’s just had no activity for months despite people opening issues. I sent them a Tweet, the CTO replied after less than an hour, and then put resources onto bringing the SDK up to scratch.
Once your PR has been accepted, you can then switch to using the original package instead of your fork in your Composer file.
Level 61
That didn't work for Docker. Opened on 31 Jan 2019. Closed on 7 Oct 2020. Hundreds of comments. Trashing on Twitter. Nothing helped.
Please or to participate in this conversation.