pcrov/jsonreader

What's Changed

• Support for PHP8.4 by @VladimirRebilly in #34

New Contributors

• @VladimirRebilly made their first contribution in #34

Full Changelog: 1.0.3...1.0.4

Relaxes the composer constraint on psr/http-message to allow for using v2.

The reader should be a bit more memory friendly if you're calling value on objects or arrays.

Dependence on the Ctype extension has been dropped. That it remained for so long is a testament to my laziness.

This release adds support for PHP 8 and drops support for PHP 7.2 and under.

The changes are purely on the testing and requirements side of things, there is nothing to consider when upgrading.

This package has been stable for quite a while now, this release just makes that official.

There are no major changes since 0.8.0.

Support for PSR-7 streams have been added with a new input stream and associated method on JsonReader, psr7Stream.

The parser has been rewritten, and along with further tweaks to the lexer and reader, makes for another performance bump.

There are no API changes in this release.

This release features an overhaul in lexing as well as other performance improvements. Things should be a bit faster.

Numbers will no longer be returned as strings from JsonReader::value(), they will instead be cast automatically to float or int as appropriate while minding the new option below.

Added

• JsonReader::FLOATS_AS_STRINGS option is now accepted by the JsonReader constructor. This will cause the reader to return floats as their original strings. This includes any JSON number with a decimal point or exponent, as well as those above PHP_INT_MAX or below PHP_INT_MIN.

Changed

• The JsonReader node constants are now strings. This makes debugging a bit easier. Note that this also changes the return type of JsonReader::type() to string.
• The parser, lexer, and input streams are no longer Traversable. Those using these directly will want to check their new simplified interfaces.
• Tuples from the lexer have a new shape to them. Again if you're using this directly you'll want to check the new interface.

Most of these we already throwing exceptions, just in the wrong place.
One particularly crafty one wasn't.

Tighten up UTF-8 verification