"Users can provide both encoded and decoded query characters. Implementations ensure the correct encoding as outlined in getQuery()." —UriInterface, PSR-7

If I'm building a library that uses PSR-7 interfaces, how do I know whether I can provide encoded or decoded query characters to the implementation, since my library doesn't know what implementation(s) it's dealing with?

#PHP #PHPFIG #PSR7

OMG! WTF kind of AI abomination is this?!

https://www.youtube.com/watch?v=ZnoRf9o9YUI

#PHP #PSR7 #PHPFIG

I'm happy to announce the release of league/uri v7 . Please head to the documentation website to see what's new and what has changed.

The goal was to make the packages easier to install, use and abuse. Hope you like it
https://uri.thephpleague.com/ #php #url #uri #psr7 #thephpleague

I will try to share some notes on the new features and the new approach to the packages

#PSR7 just got 2 new tags! The evolution vote passed, and we got:

1.1 with argument types
2.0 with return types

Both require PHP 7.2; more details available in the PSR meta doc, section 7.2, "Type additions": https://www.php-fig.org/psr/psr-7/meta/#72-type-additions

Do you use #psr7 in #php? I've finally opened the PSR Evolution vote to add parameter and return type declarations:

https://groups.google.com/g/php-fig/c/BChJkYoIpRM/m/gbSivVypBQAJ

Two week comment period, hopefully followed by a vote. Would love feedback; my review of the proposed patches looks very promising so far!