adds JSON_ERROR_NON_BACKED_ENUM to allowed JSON::encode() errors.

[ju1ius]

The JSON_ERROR_NON_BACKED_ENUM error code is not yet documented (see php/doc-en#2747), but it is returned when trying to encode encode a non-backed enum to JSON.

Since this error code is semantically equivalent to JSON_ERROR_UNSUPPORTED_TYPE which is already in the allow list, it makes sense to also add it.

For context, I was adding a Monolog record as a Breadcrumd metadata item, which looked like this:

[
    'type' => 'default',
    'category' => 'doctrine',
    'level' => 'debug',
    'timestamp' => 1709047886.0,
    'message' => 'Executing statement: {sql} (parameters: {params}, types: {types})',
    'data' => [
        'sql' => 'SELECT id, key FROM ... WHERE id = ? AND key = ?',
        'params' => [42, 'somekey'],
        'types' => [
            \Doctrine\DBAL\ParameterType::INTEGER,
            \Doctrine\DBAL\ParameterType::STRING,
        ],
    ],
],

The encoding error is triggered by Doctrine\DBAL\ParameterType, which is a unit enum in Doctrine DBAL v4.
Since the JSON_ERROR_NON_BACKED_ENUM is not handled by JSON::encode(), this caused an exception to be thrown in PayloadSerializerInterface::serialize() and as a result the whole event was ignored (nothing was sent to the sentry endpoint).

[cleptric]

Please add a test for this. You can skip it on PHP versions that do not support JSON_ERROR_NON_BACKED_ENUM.

[cleptric]

Thanks

[ju1ius]

Thanks

You're welcome

[cleptric]

This was released with 4.6.1.