- 217comments
- 50comments
- 7comments
- 108comments
- 2comments
- 100comments
- 2comments
- 118comments
- 16comments
- 218comments
- 12comments
- 29comments
- 74comments
- 44comments
- 53comments
- 4comments
- 303comments
- 34comments
- 243comments
- 43comments
- 54comments
- 25comments
- 72comments
- 22comments
- 3comments
- 7comments
- 219comments
- 17comments
- 49comments
- 15comments
Author here, happy to answer any questions. I never imagined a polyfill for http_build_url would gain so much traction. After 12 years, deprecating it feels like the right move, especially given the new options from the community and PHP itself.
We used to work together at AOL. Glad to see you on here; I hope you're doing great!
Reading this threw me back to 2014 - how was working for AOL back then?
Love you kept it alive this long
There is nothing as permanent as a temporary fix that works.
For a package with that kind of install base, is there a final release that prints the migration options in a deprecation notice? People will find it years from now through old Stack Overflow answers.
The package is marked as abandoned on Packagist [1]
Both adding it as a dependency using composer and installing it from a lockfile results in:
[1] https://packagist.org/packages/jakeasmith/http_build_url