Fix JSON parsing with hexadecimal characters

[zjeffer]

Fixes #2495 and #2475

The JSON spec doesn't allow characters like \xab. Instead, it should be converted to unicode: \u00ab.

It's my first time writing catch2 tests, let me know if I did something wrong.

[zjeffer]

@Nyayurn can you test if you still have your bug with this new parser?

[Nyayurin]

@Nyayurn can you test if you still have your bug with this new parser?

It's fine

[Nyayurin]

But it's a new bug with clock, in screenshot's right top the clock compoment do not work

[zjeffer]

Can you show the console output, I'd like to see if there are any errors from the clock component.

[Nyayurin]

and the config

[zjeffer]

@Nyayurn with your config, I get the same error on latest master.
Something seems to be wrong with your format string..

I think the clock icon needs to be outside of the {} brackets, like this: "<icon>{:%I:%M %p %d/%m/%Y}"

It works for me on both latest master and this PR:

[Nyayurin]

@Nyayurn with your config, I get the same error on latest master. Something seems to be wrong with your format string..

I think the clock icon needs to be outside of the {} brackets, like this: "<icon>{:%I:%M %p %d/%m/%Y}"

It works for me on both latest master and this PR:

Thanks, It's work now

[zjeffer]

@Alexays This is ready to be reviewed.

[Alexays]

LGTM, thx for this fix!