JsonApiSerializer resourceKey and cursor about fractal

[jasonlewis]

I believe I pushed a fix for this. You can set the resource key as the last
parameter to withCollection.
On 30 Jun 2014 13:09, "bpudenz" [email protected] wrote:

I'm getting "The $resourceKey parameter must be provided when using
League\Fractal\Serializer\JsonApiSerializer" when combining this with a
cursor:

$cursor = new Cursor($currentCursorStr, $newCursorStr, $users->count());

return Response::api()->withCollection($users, new UserTransformer,
$cursor);

I see resourceKey in the serializer docs.. is this currently incompatible
with dingo/api?

—
Reply to this email directly or view it on GitHub
#80.

[bpudenz]

return Response::api()->withCollection($users, new UserTransformer, $cursor, 'users');

Gives me the same result. In the Fractal docs, the third parameter is $resourceKey, in the Api, it's a cursor = null.

[jasonlewis]

Try updating to the latest 0.7.* version of the API if you haven't already.
I just looked, it definitely had the resource key as the fourth parameter
which is then used as the third parameter when creating a new collection
resource.
On 30 Jun 2014 13:30, "bpudenz" [email protected] wrote:

return Response::api()->withCollection($users, new UserTransformer,
$cursor, 'users');

Gives me the same result. In the Fractal docs, the third parameter is
$resourceKey, in the Api, it's a cursor = null.

—
Reply to this email directly or view it on GitHub
#80 (comment).

[bpudenz]

Checking versions does the job. It looks like that fixes it when I move the Route outside the 'protected' => true group, but when I leave it in and pass a valid access_token, I get:

call_user_func() expects parameter 1 to be a valid callback, no array or string given

I wasn't getting this before. Did something else change between 0.6.* and 0.7.* that would cause this? I'm simply pointing to:

Route::api(['version' => 'v1', 'protected' => true], function()
{
Route::get('user', 'UserController@index')
}];

[jasonlewis]

Yeah check the issues on the API package, also check
https://github.com/dingo/api/wiki/Changes regularly.
On 30 Jun 2014 14:00, "bpudenz" [email protected] wrote:

Checking versions does the job. It looks like that fixes it when I move
the Route outside the 'protected' => true group, but when I leave it in and
pass a valid access_token, I get:

call_user_func() expects parameter 1 to be a valid callback, no array or
string given

I wasn't getting this before. Did something else change between 0.6.* and
0.7.* that would cause this? I'm simply pointing to:

Route::api(['version' => 'v1', 'protected' => true], function()
{
Route::get('user', 'UserController@index')
}];

—
Reply to this email directly or view it on GitHub
#80 (comment).

[bpudenz]

thanks

[philsturgeon]

Looks like you guys have this one figured out, and its not directly a Fractal thing anyhow. :)