[Bug]: "Trying to access array offset on null" on text 'null' value

[andrewpros]

PHP Version

8.4.3

Version

2.0.0

Bug Description

Setting content with SetContent to text 'null' throws an error "Trying to access array offset on null" in vendor\\ueberdosis\\tiptap-php\\src\\Core\\Schema.php:70

Its because in https://github.com/ueberdosis/tiptap-php/blob/2.0.0/src/Editor.php#L45
getContentType is called https://github.com/ueberdosis/tiptap-php/blob/2.0.0/src/Editor.php#L96
and verifies the value using json_decode, but this accepts literal 'null' text as valid null

So in turn apply will get a null document https://github.com/ueberdosis/tiptap-php/blob/2.0.0/src/Core/Schema.php#L70

and throw

Expected Behavior

Be able to edit any text value, including 'null'

Additional Context (Optional)

I only found about this by chance using laravel filament RichEditor that is using this package under the hood.
The input data is external and imported to db, and there was some 'null' text in some of the fields.

Thats why there is also ready to test filament repo with this case as it was reported as filament issue here filamentphp/filament#18216 but closed due the issue being in the package

Dependency Updates

• Yes, I've updated all my dependencies.

[SpaceofWeb]

Any progress on this?

I encountered same error but with string '123'. Type casting did nothing.

{
  "message": "Trying to access array offset on int",
  "exception": "ErrorException",
  "file": "/Users/space/dev/work/backend/vendor/ueberdosis/tiptap-php/src/Core/Schema.php",
  "line": 70,
}

I found that root problem is here:
src/Editor.php:91

if (is_string($value)) {
    try {
        /**
         * @psalm-suppress UnusedFunctionCall
         */
        json_decode($value, true, 512, JSON_THROW_ON_ERROR);
        return 'JSON';
    } catch (Exception $exception) {
        return 'HTML';
    }
}

Code checks if it is a string and then successfully json decodes it.

is_string(123)
= false

> is_string('123')
= true

> json_decode('123', true, 512, JSON_THROW_ON_ERROR);       
= 123

Then later in the code '123' as json will throw an error.
I think it should somehow check if it an actual json and not a string with numbers.

[SpaceofWeb]

I've successfully fixed problem with this code:

if (is_string($value)) {
    try {
        /**
         * @psalm-suppress UnusedFunctionCall
         */
        $decoded = json_decode($value, true, 512, JSON_THROW_ON_ERROR);

        if (is_array($decoded)) {
            return 'JSON';
        }
        return 'HTML';
    } catch (Exception $exception) {
        return 'HTML';
    }
}

if (is_array($value)) {
    return 'Array';
}

But then I saw PR #76 that fixes this problem.
Can anybody merge it?