Escaped backslashes or unicode in json

[sammyjo20]

Escaped backslashes or unicode in json

[Sammyjo20]

Hey @Whizboy-Arnold really sorry for the delay on this!

I will get a fix out for you soon which will allow you to customise the JSON flags.

[juse-less]

@Sammyjo20 Hey.

I think what @Whizboy-Arnold means is that he'd like to add/overwrite the JSON flags in the JsonBodyRepository.
JSON should be escaped, like PHP does, but isn't required.
AFAIK, most people also don't escape it, unlike PHP.
I've also faced issues with escaped JSON in the past, where APIs don't actually support JSON, even though that's their 'data format'.
So I can relate to the situation.

That being said, you should be able to straight-off snag my 'HasJsonFlags' trait in my private concept repo (src/Concerns/HasJsonFlags), you've been invited to.
Then you should be able to add it to the JsonBodyRepository, and change

public function __toString(): string
{
    return json_encode($this->all(), JSON_THROW_ON_ERROR);
}

to something like

public function __toString(): string
{
   $json = is_null($this->getJsonFlags())
        ? json_encode($this->all())
        : json_encode($this->all(), $this->getJsonFlags());

    // If JSON_THROW_ON_ERROR is not set, turn `false` into an empty string.
    return $json === false ? '' : $json;
}

Or if you want to enforce a JSON Exception, something like:

public function __toString(): string
{
    return json_encode($this->all(), $this->getJsonFlags() | JSON_THROW_ON_ERROR);
}

Keep in mind, though, if this is done - using interface type hints will not resolve the new JSON flag methods.

[Sammyjo20]

Sorry I'm a little confused @Whizboy-Arnold - do you mind clarifying a little bit? Thanks!

[Whizboy-Arnold]

Ok thank you for the support

[Sammyjo20]

Hey @Whizboy-Arnold I've made a PR (#229) to add support for this. Please could you take a look over it to see if it would be suitable for you?