json_decode AND json_encode long integers without losing data

As long as your PHP version can actually handle large integers, meaning if you're running a 64-bit version of PHP ^{(on something other than Windows)}, json_decode has no problem with it:

$json  = '{"foo":9223372036854775807}';$obj   = json_decode($json);$json2 = json_encode($obj);var_dump(PHP_INT_MAX, $obj, $json2);int(9223372036854775807)object(stdClass)#1 (1) {  ["foo"]=>  int(9223372036854775807)}string(27) "{"foo":9223372036854775807}"

If the integer values you need to handle do exceed PHP's PHP_INT_MAX, you simply cannot represent them in PHP native types. So there's no way around the conundrum you have; you cannot use native types to track the correct type, and you cannot substitute other types (e.g. strings instead of integers), because that's ambiguous when encoding back to JSON.

In this case you will have to invent your own mechanism of tracking the correct types for each property and handle such serialisation with a custom encoder/decoder. For example, you'd need to write a custom JSON decoder which can decode to a custom class like new JsonInteger('9223372036854775808'), and your custom encoder would recognise this type and encode it to a JSON 9223372036854775808 value.

There's no such thing built into PHP.

For what it's worth, PHP can support values > PHP_INT_MAX using the bcmath package http://php.net/manual/en/book.bc.php but JSON is a slightly more difficult issue.

To answer the OP's question of why they can't encode the value from a string back to an int type in the JSON, the answer lies in the conversion step. When reading the original JSON string in, it's a string, and read byte by byte. When reading values, they're initially read as a string (as the JSON itself if a string), and later cast to the correct type to an int or a float depending upon the presence of a period (.). If the value is greater than PHP_INT_MAX then PHP converts it to a double, and you lose precision. Thus using JSON_BIGINT_AS_STRING will tell the parser to keep the value as a string and NOT try to cast it, everything should be good, the value is kept in tact, albeit a string.

The problem comes when doing the inverse, and doing json_encode($value, JSON_NUMERIC_CHECK) tells PHP to cast string numeric values into either int/float, but this appears to happen BEFORE writing to the JSON string, causing values > PHP_INT_MAX to be converted into a double representation like 9.2233720368548e+19

See https://3v4l.org/lHL62 or below:

$bigger_than_max = '{"max": ' . PHP_INT_MAX . '1}'; // appending 1 makes > PHP_INT_MAXvar_dump($bigger_than_max);var_dump(json_decode($bigger_than_max));var_dump(json_decode($bigger_than_max, false, 512, JSON_BIGINT_AS_STRING));var_dump(json_encode(json_decode($bigger_than_max, false, 512, JSON_BIGINT_AS_STRING)));var_dump(json_encode(json_decode($bigger_than_max, false, 512, JSON_BIGINT_AS_STRING), JSON_NUMERIC_CHECK));

Result:

string(29) "{"max": 92233720368547758071}"object(stdClass)#1 (1) {  ["max"]=>  float(9.2233720368548E+19)}object(stdClass)#1 (1) {  ["max"]=>  string(20) "92233720368547758071"}string(30) "{"max":"92233720368547758071"}"string(29) "{"max":9.223372036854776e+19}"

Unfortunately, it doesn't appear that there is a way to solve this, looking at the JSON constants http://php.net/manual/en/json.constants.php I don't see anything that allows you to write integer values > PHP_INT_MAX into ints within the JSON.

Sorry this doesn't find a solution but hopefully clears up some confusion.