Scramble does not recognise if wrapper is already contained in resource.

[mihob]

If the toArray function of a resource already contains the wrapper (data), Laravel will not wrap the result again. Scramble does not take this into account.

[romalytvynenko]

@mihob Please share the examples so I can reproduce. Thanks!

[mihob]

For example

class MyResource extends JsonResource
{
    /**
     * Transform the resource into an array.
     *
     * @return array<string, mixed>
     */
    public function toArray(Request $request): array
    {
        return [
            'foo' => $this->foo,
            'bar' => $this->bar,
            'data' => $this->something
        ];
    }
}

Laravel will not wrap the Result in data because it is already present in the returned array, the json response will look like this:

{
    'foo': '....',
    'bar': '....',
    'data': '....'
}

But scramble does not take this into account and the says the response will look like this:

{
    'data':  {
        'foo': '....',
        'bar': '....',
        'data': '....'
    }
}

Does that help you? @romalytvynenko

[mihob]

Here you can see how the decision is made as to whether the data is wrapped again.

vendor/laravel/framework/src/Illuminate/Http/Resources/Json/ResourceResponse.php

function wrap(...) and function haveDefaultWrapperAndDataIsUnwrapped(...)/function haveAdditionalInformationAndDataIsUnwrapped(...)