Releases: TRowbotham/URL-Parser
Releases · TRowbotham/URL-Parser
3.0.0
See CHANGELOG.md
2.0.3
Fixed
- "%2e%2E" and "%2E%2e" were not properly detected as percent encoded double dot path segments.
2.0.2
- Fixes some compatibility issues with PHP 7.4.
- Removes some unnecessary type casting when serializing IP addresses.
2.0.1
Fixes an issue loading cached test data when using newer versions of the symfony/cache component.
2.0.0
- The minimum required PHP version is now 7.1
- Native typehints are now used. This which means that an
\TypeError
is now thrown instead of an\InvalidArgumentException
when a value with an incorrect type is passed. - Tests now automatically pull the latest data directly from the Web Platform Tests repository.
\Rowbot\URL\Exception\TypeError
and\Rowbot\URL\Exception\InvalidParserState
now inherit from\Rowbot\URL\Exception\URLException
1.1.1
- Fixes the query string sorting algorithm
- Speeds up URLSearchParams::has() when the string does not exist in the list.
- Added TravisCI automation for tests and code coverage.
1.1.0
- Only scalar values (bool, float, int, string) and objects with a
__toString()
method are considered as valid input now for methods and properties that only accept strings. This matches what PHP's string type hint would allow, allowing for an easier upgrade path when adding native type hints in the future.- A
null
value is no longer considered valid input and will cause an\InvalidArgumentException
to be thrown. Previously, this was converted to the string"null"
. - A
resource
value such as that returned by a call tofopen()
is no longer considered valid input and will cause an\InvalidArgumentException
to be thrown. This was previously casted to a string resulting in something like"Resource id #1"
. - Previously, the values
true
andfalse
were converted to the strings"true"
and"false"
. This is no longer the case. They now are now simply cast to a string resulting in the values"1"
and""
respectively.
- A
- Passing an
iterable
that does not solely contain otheriterables
to theURLSearchParams
constructor now causes it to throw an\InvalidArgumentException
. - Trying to access an invalid property on the
URL
object will now throw an\InvalidArgumentException
to help catch typos. - Updated documentation
- Updated tests
1.0.3
- Speeds up the serialization of IPv6 addresses.
- URLs with special schemes now percent encode
'
characters in the query string. - Simplifies the application/x-www-urlencoded algorithm.
- Improves handling of query strings with non-UTF-8 encodings.
- Adds a bunch of missing use declarations.
- Updates to tests and test resources.
1.0.2
- Trying to set URL::searchParams directly will now throw a TypeError.
- Passing invalid input will now throw an InvalidArgumentException.
- Malformed byte sequences should now get fixed up with \uFFFD replacement characters.
- URLSearchParams now implements Iterator instead of IteratorAggregate to match test expectations.
- The last few failing tests are now passing with the exception of 3 errors as a result of PHP bug 72506.
1.0.1
Add license