You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a heads up for anyone going through the last module, it seems there's an issue with the assertQueryStringHas assertion, due to a change to the assertHasQueryStringParameter method that it calls. Basically, assertHasQueryStringParameter now returns $this (i.e. the Laravel\Dusk\Browser object) instead of the $output array which contains the query string key/value pairs.
So having something like $browser->assertQueryStringHas('response_type', 'code') will cause a "Error: Cannot use object of type Laravel\Dusk\Browser as array" error when it gets to this part of the assertQueryStringHas method:
PHPUnit::assertEquals(
$value, $output[$name],
"Query string parameter [{$name}] had value [{$output[$name]}], but expected [{$value}]."
);
Just a heads up for anyone going through the last module, it seems there's an issue with the
assertQueryStringHas
assertion, due to a change to theassertHasQueryStringParameter
method that it calls. Basically,assertHasQueryStringParameter
now returns$this
(i.e. the Laravel\Dusk\Browser object) instead of the$output
array which contains the query string key/value pairs.So having something like
$browser->assertQueryStringHas('response_type', 'code')
will cause a "Error: Cannot use object of type Laravel\Dusk\Browser as array" error when it gets to this part of theassertQueryStringHas
method:I've opened an issue here: laravel/dusk#455.
Here's the commit that causes the issue: laravel/dusk@fb67e61
Cheers!
The text was updated successfully, but these errors were encountered: