Having the following JSON:

{ "key" : "Hello, world!" }

and parsing it using

\Zend\Json\Json::prettyPrint('{ "key" : "Hello, world!" }', ["indent" => ""]);

will produce:

{"key":"Hello,world!"}

The reason is first line from \Zend\Json\Json::prettyPrint

$tokens = preg_split('|([\{\}\]\[,])|', $json, -1, PREG_SPLIT_DELIM_CAPTURE);

not taking into account that a comma could resides inside a token.

This PR

• [x] asserts that a space after a , in string value is left alone
• [x] leaves the space after a , in a string value alone

Fixes #2.

💁‍♂️ Not sure if a fix yet, but figured I provide a failing test at least.

This PR

• [x] asserts that empty arrays and objects are printed without new lines
• [x] looks ahead for closing brackets and skips new lines if there's only whitespace in-between

Check code blocks are correct

TLDR; Check in all files that codeblocks are correct, in PSR-2 format and have PHP syntax highlighting applied.

Code blocks should be in the following format...

```php
 'ZEND-FRAMEWORK');

// No required options
$rendererOptions = array();
$renderer = Barcode::factory(
    'code39', 'image', $barcodeOptions, $rendererOptions
);

```

Note the three backticks then php in the opening fence, and the closing fence is just three backticks. It's common for the opening backticks to have no code type, or something like source.

Code should also have been automatically formatted into PSR-2 format, but sometimes these slip through the net.

PHP Deprecated: Array and string offset access syntax with curly braces is deprecated in zendframework\zend-json\src\Decoder.php on line 110 PHP Deprecated: Array and string offset access syntax with curly braces is deprecated in zendframework\zend-json\src\Decoder.php on line 365 etc

I have a code like this.

$customer= $this->entityManager->getRepository(Customer::class)->findOneById('5'); $jsonObject = \Zend\Json\Json::encode($customer,true); print_r($jsonObject); die;

However the output becomes empty/nothing. No errors either from PHP or the ZF3 I can assure, all the data properties of Class Customer are set to public. Where would be the problem?

From Fedora QA: https://apps.fedoraproject.org/koschei/package/php-zendframework-zend-json?collection=f28

PHPUnit 5.7.23 by Sebastian Bergmann and contributors.
Runtime:       PHP 7.2.0RC4
Configuration: /builddir/build/BUILD/zend-json-f42a1588e75c2a3e338cd94c37906231e616daab/phpunit.xml.dist
..................................PHP Fatal error:  Cannot use 'Object' as class name as it is reserved in /builddir/build/BUILD/zend-json-f42a1588e75c2a3e338cd94c37906231e616daab/test/TestAsset/Object.php on line 13

Having issue when query the column contains encoded data however sql query below works fine for encoded data by json_encode func,

Query SELECT * FROM bidtaxi_master.errorlog WHEREInfoIS NOT NULL and JSON_EXTRACT(Resource, "$.env\'") = "sandbox\'";

Is there any other sql statement I can use for json query encoded by this component or doctrine?

Check the document for bad blockquoutes

TLDR; Check blockquotes are formatted correctly using > and check headings in blockquotes are using ###

Blockquotes are donated by a single greater than character and then a space. Make sure all the blockquotes in every doc file are correctly formatted. Headings in blockquotes should use ### and not bold.

Any paragraph spacing in blockquotes should be marked using a single greater than, then a space.

Check the tables in a document

TLDR; All tables should be in the format of GHFM using | and - as horizontal and vertical separators respectively

Check all tables are in the correct format. Please don't use leading and trailing | - more information on github flavoured markdown tables can be found here.

Check docs for other problems

TLDR; Cast your eye over the documetation for any problems not covered in the other issues

Things slip through the net, so check the documentation for other problems that have been missed. Common other problems include

• Bullet lists (should be single * then space at the start of line)
• Inline code - should be marked by three backticks at start and finish
• bookdown.json file is correctly formated and has the right escaping
• Links between documentation using RST have been stripped
• Any other RST has been removed correctly
• Anything and everything not covered

If you end up fixing the same problem over and over, please ping Gary Hockin - we may be able to add bespoke issue for that problem, or fix in automated capacity

Adding the new "forceObject" flag to be passed to the encoder in the options in the manner of ['forceObject' => true,] . This then forces the encoder output to encode to an object rather than an array. This implementation assumes all nested arrays to be forced to be objects in the manner of JSON_FORCE_OBJECT.

This is the pull request for the conversation outlined in #27

there is a problem when json_encode get an incorrect character but i have a solution: in Json.php

private static function encodeViaPhpBuiltIn($valueToEncode, $prettyPrint = false)
{
    if (! function_exists('json_encode') || static::$useBuiltinEncoderDecoder === true) {
        return false;
    }

    $encodeOptions = JSON_HEX_TAG | JSON_HEX_APOS | JSON_HEX_QUOT | JSON_HEX_AMP;

    if ($prettyPrint) {
        $encodeOptions |= JSON_PRETTY_PRINT;
    }
    array_walk_recursive($valueToEncode, function(&$item, $key){
        if(!mb_detect_encoding($item, 'utf-8', true)){
            $item = utf8_encode($item);
        }
    });
    $encoded = json_encode($valueToEncode, $encodeOptions | JSON_UNESCAPED_UNICODE | JSON_UNESCAPED_SLASHES);
    return $encoded ? $encoded : json_last_error_msg();
}

The new section is from array_walk_recursive().

There is no way to modify json_encode() encode options except JSON_PRETTY_PRINT. For example we can't enable JSON_UNESCAPED_UNICODE or disable default options.

Extending the base class Zend\Json\Json as workaround creates another problems - can't use JsonRenderer with another Json encoder, Zend\Json\Json only: https://github.com/zendframework/zend-view/blob/master/src/Renderer/JsonRenderer.php#L127-L170

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html

Original Issue: https://api.github.com/repos/zendframework/zendframework/issues/7544 User: @dreadnought78 Created On: 2015-05-23T22:04:16Z Updated At: 2015-11-06T23:57:01Z Body If the user forgot or send some required parameter with a wrong name the server returns the error ERROR_INVALID_PARAMS.

This request added a invalid parameters list in the json response.

Result before

{
    "error":{
        "code":-32602,
        "message":"Invalid params",
        "data":null
    },
    "id":"8",
    "jsonrpc":"2.0"
}

Result after

{
    "error":{
        "code":-32602,
        "message":"Invalid param(s): [estimatedMonths, location, specieId, coatTypeId]",
        "data":null
    },
    "id":"8",
    "jsonrpc":"2.0"
}

*Please do not consider this pull request if this implementation has not been made before for security reasons.