Update type specifiers in validation logging

[talldan]

Description

Noticed while debugging a validation issue with a full-content test I'm working on. The warning logged had some incorrect formatting.

I was receiving the following error, which I initially found confusing:

"Expected attributes 0, instead saw 0."

I tracked this down to the line of code:

log.warning( 'Expected attributes %o, instead saw %o.', expected, actual );

According to the sprintf-js docs, %o is for an octal, so that explains the zeros. This PR changes the instances of %o to %j, which the library says will output a json representation of the parameter.

Tested and I received a better error, still not perfect, but an improvement:

["Expected attributes [], instead saw [[\"scope\",\"col\",true]]."]

I imagine this came about because of an update to the library or change of library used for those messages.

How has this been tested?

Detailed above. I reproduced by creating a validation error in one of the full-content tests (adding an attribute that wasn't produced in the save content), and then regenerating the fixtures. Jest will output the error in the terminal.

Screenshots

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.

[gziolo]

Good catch. I double checked sprintf-js docs and your proposal makes the most sense 👍

I trust you and haven't tested it myself :)

[aduth]

I must have thought %o was for "object" 🤦‍♂Thanks for fixing.