You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apparently it's a good idea to use PSR-7 when writing libraries that implement URLs, Requests, Responses, etc. but I'm coming to the opinion that it really doesn't matter at all, and PSRs actually just get in the way of what you're trying to do.
If this library's intention was to be interoperable with other Http libraries, maybe it would be a good idea to implement PSRs, but who has ever inter-operated anything in PHP? You refactor and get the job done.
This is not a rant about PSR. It's great to have consistency. But this library is suffering, because PSRs are not compatible with web standards.
The text was updated successfully, but these errors were encountered:
The main area of confusion is within classes surrounding Uri. The web standards call this class URL and it has a completely different set of methods and properties.
The knock on effect of dropping support will require a massive load of unpicking, but it would mean more web standards compliance, which is much more important to me and this library.
Apparently it's a good idea to use PSR-7 when writing libraries that implement URLs, Requests, Responses, etc. but I'm coming to the opinion that it really doesn't matter at all, and PSRs actually just get in the way of what you're trying to do.
If this library's intention was to be interoperable with other Http libraries, maybe it would be a good idea to implement PSRs, but who has ever inter-operated anything in PHP? You refactor and get the job done.
This is not a rant about PSR. It's great to have consistency. But this library is suffering, because PSRs are not compatible with web standards.
The text was updated successfully, but these errors were encountered: