-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Exception throw on a fresh installation of laravel & dingo-api #1584
Comments
Try this:
|
Hi thanks , yes the debugger still stoping there with that error message.
|
Can be closed, the package just needs to be tagged (as there's been many fixes lately). @thilanga |
I get this problem with Digno 2.1.0 For now I've fixed it by adding to my AppServiceProvider public function register()
{
$this->app->bind("League\\Fractal\\ScopeFactoryInterface", "\\League\\Fractal\\ScopeFactory");
//
} |
Can you please submit a new issue if it's a problem @gruz |
Actual Behaviour
Exception is thrown after performing any php artisan command while in debug mode in a fresh laravel with dingo setup.
Expected Behaviour
There should be no exceptions
Steps to Reproduce
After installing fresh Laravel then adding Dingo package then starting debug mode in my VSCode an exception is thrown after performing any php artisan command ,
Example : php artisan serve ( with debug mode )
will give
PHP Fatal error: Uncaught Illuminate\Contracts\Container\BindingResolutionException: Target [League\Fractal\ScopeFactoryInterface] is not instantiable while building [Dingo\Api\Transformer\Adapter\Fractal, League\Fractal\Manager]. in /laravel/testapi/vendor/laravel/framework/src/Illuminate/Container/Container.php:933
if you are not running the debug mode you will not see the error at all , but I guess this might be affecting some other behaviour (I'm not sure ) for example when trying to generate documentation I'm getting empty file with only titles so I tried to debug there and I encountered this issue but I'm not sure what are side effects of it .
The text was updated successfully, but these errors were encountered: