Feature | JSON flags on JsonBodyRepository

[Sammyjo20]

Fixes #194

This PR adds support to customise the JSON flags that are used to encode the JSON body repository in Saloon. For example, if you want to make sure that body that contains slashes doesn't get escaped, you can use the setJsonFlags method on the body method to overwrite them.

They use a "bitmask" which is slightly different from arrays. For example, to set both JSON_THROW_ON_ERROR and JSON_UNESCAPED_SLASHES you would need to separate them with a pipe (|)

$request = new GetServersRequest;
$request->body()->setJsonFlags(JSON_THROW_ON_ERROR | JSON_UNESCAPED_SLASHES);

$connector->send($request);

As Saloon recommends keeping logic standardised inside of requests, I would recommend that you set this within the __construct or the boot method of the request...

__construct()
{
     $this->body()->setJsonFlags(JSON_THROW_ON_ERROR | JSON_UNESCAPED_SLASHES);
}

Side note, @juse-less - any idea why it seems like it's ignoring our baseline file now and spitting out loads of the "ignored" errors?

[Sammyjo20]

Self review

[what-the-diff]

PR Summary 🎉

• Introducing $jsonFlags for JsonBodyRepository 💡
  Allows you to customize the JSON encoding process.

• Getter and Setter methods for jsonFlags 🛠️
  For added ease in customizing your JSON encoding experience.

• Improved error handling with JSON_THROW_ON_ERROR 🚀
  Now throws exceptions during errors instead of staying silent, making debugging a breeze! 😃

[juse-less]

@Sammyjo20 I believe it's because the lock file isn't checked into the repo, so you'll always get the newest PHPStan version.

They recently fixed a couple things on how they interpret callables, so I reckon that's related.

[Sammyjo20]

@juse-less Thanks 👍 I managed to fix it by rebuilding the ignores :)