-
Notifications
You must be signed in to change notification settings - Fork 611
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
ERROR: htmlspecialchars() expects parameter 1 to be string, array given #353
Comments
same issue |
Can I get more of a stack trace, please?
|
` ErrorException : htmlspecialchars() expects parameter 1 to be string, array given (View: /Users/evgeny/Documents/Code/jwt/vendor/mpociot/laravel-apidoc-generator/src/resources/views/partials/route.blade.php) at /Users/evgeny/Documents/Code/jwt/vendor/laravel/framework/src/Illuminate/Support/helpers.php:578
Exception trace: 1 Illuminate\View\Engines\CompilerEngine::handleViewException(Object(ErrorException)) 2 Mpociot\ApiDoc\Commands\GenerateDocumentation::Mpociot\ApiDoc\Commands{closure}() Please use the argument -v to see more details. |
public function rules() |
I also faced with such issue. I noticed the following: |
This should be fixed now (2.1.7) |
I'm not actually sure where the issue is coming from, but suddenly our deployer stopped working because of this..
htmlspecialchars() expects parameter 1 to be string, array given (View: /Users/marvinquezon/codes/cms/vendor/mpociot/laravel-apidoc-generator/src/resources/views/partials/route.blade.php) {"exception":"[object] (ErrorException(code: 0): htmlspecialchars() expects parameter 1 to be string, array given (View: /Users/marvinquezon/codes/cms/vendor/mpociot/laravel-apidoc-generator/src/resources/views/partials/route.blade.php) at /Users/marvinquezon/codes/cms/vendor/laravel/framework/src/Illuminate/Support/helpers.php:560, ErrorException(code: 0): htmlspecialchars() expects parameter 1 to be string, array given at /Users/marvinquezon/codes/cms/vendor/laravel/framework/src/Illuminate/Support/helpers.php:560)
The text was updated successfully, but these errors were encountered: