-
-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[9.x] Breaking change due to improved error handling #408
Comments
There no reason for Testbench to know about the class when Laravel Framework will resolved it via |
I did quick debugging when I checked it but ... that method, which registered it in the framework, was never called in my test? |
orchestral/testbench-core@e5a07ba This tests would have failed if what you are claiming is true. You need to submit failing tests before I can debug anything. |
That was the missing link! In my case, I saw in your test the Thanks 🙏🏼 |
Description:
I'm not sure where to go with this, but I think it might be related to testbanch.
Since laravel/framework#51261 the tests at graphql-laravel are failing with L11
prefer-stable
and they work withprefer-lowest
.I think this is because in the latest framework, there's a new class
\Illuminate\Foundation\Exceptions\Renderer\Renderer
registered in\Illuminate\Foundation\Providers\FoundationServiceProvider::registerExceptionRenderer
That class last argument,
string $basePath
, can't be automagically resolved and needs to be provided.I think due to this new changes, testbench does not know about this class and therefore does not register it and we and up with this error:
Stacktrace (manually converted a bit, due to mixed with HTML
Steps To Reproduce:
\Rebing\GraphQL\Tests\Database\EmptyQueryTest::testNoExplicitContentType
Sorry if this is the wrong package, I tried at the Larvel project but was told they can't help me.
The text was updated successfully, but these errors were encountered: