在我今天得到的PHP Intelephense的最新更新之后，Intelephense一直显示我的路由(和其他类)的未定义符号的错误，以前没有这样的错误，它困扰着我。
以下是错误截图:
这是我的代码:
Route::group(['prefix' => 'user', 'namespace' => 'Membership', 'name' => 'user.'], function () {
Route::get('profile', 'ProfileController@show')->name('profile.show');
Route::patch('profile', 'ProfileController@update')->name('profile.update');
Route::patch('change-password', 'ChangePasswordController@change')->name('change-password');
Route::get('role', 'ProfileController@getRole')->name('profile.role');
Route::get('summary', 'SummaryController@show')->name('summary');
Route::get('reserved', 'AuctionController@reservedAuction')->name('reserved');
});
实际上，这段代码中没有错误，但intelephense一直显示错误，所以有办法解决这个问题吗?
对于遇到这些问题并对禁用一整套检查感到不安的人来说，有一种方法可以将您自己的自定义签名传递给Intelephense。
摘自Intelephese repo的评论(来自@KapitanOczywisty):
https://github.com/bmewburn/vscode-intelephense/issues/892#issuecomment-565852100
For single workspace it is very simple, you have to create .php file
with all signatures and intelephense will index them.
If you want add stubs globally, you still can, but I'm not sure if
it's intended feature. Even if intelephense.stubs throws warning about
incorrect value you can in fact put there any folder name.
{
"intelephense.stubs": [
// ...
"/path/to/your/stub"
]
}
Note: stubs are refreshed with this setting change.
You can take a look at build-in stubs here:
https://github.com/JetBrains/phpstorm-stubs
在我的情况下，我需要dspec的描述，beforeEach，它…不被突出显示为错误，所以我只是包括签名/ directores_and_paths /app/vendor/bin/dspec文件在我的VSCode的工作空间设置，其中有我需要的函数声明:
function describe($description = null, \Closure $closure = null) {
}
function it($description, \Closure $closure) {
}
// ... and so on
对于遇到这些问题并对禁用一整套检查感到不安的人来说，有一种方法可以将您自己的自定义签名传递给Intelephense。
摘自Intelephese repo的评论(来自@KapitanOczywisty):
https://github.com/bmewburn/vscode-intelephense/issues/892#issuecomment-565852100
For single workspace it is very simple, you have to create .php file
with all signatures and intelephense will index them.
If you want add stubs globally, you still can, but I'm not sure if
it's intended feature. Even if intelephense.stubs throws warning about
incorrect value you can in fact put there any folder name.
{
"intelephense.stubs": [
// ...
"/path/to/your/stub"
]
}
Note: stubs are refreshed with this setting change.
You can take a look at build-in stubs here:
https://github.com/JetBrains/phpstorm-stubs
在我的情况下，我需要dspec的描述，beforeEach，它…不被突出显示为错误，所以我只是包括签名/ directores_and_paths /app/vendor/bin/dspec文件在我的VSCode的工作空间设置，其中有我需要的函数声明:
function describe($description = null, \Closure $closure = null) {
}
function it($description, \Closure $closure) {
}
// ... and so on
Intelephense 1.3增加了未定义的类型、函数、常量、类常量、方法和属性诊断，而之前在1.2中只有未定义的变量诊断。
一些框架的编写方式为用户提供了方便的快捷方式，但使得静态分析引擎很难发现运行时可用的符号。
像https://github.com/barryvdh/laravel-ide-helper这样的存根生成器有助于填补这里的空白，并且通过提供易于发现的符号的具体定义，将其与Laravel一起使用将解决许多错误诊断问题。
不过，PHP是一种非常灵活的语言，根据代码的编写方式，可能会出现其他错误的未定义符号。因此，从1.3.3开始，intelephense有配置选项来启用/禁用每一类未定义符号，以适应工作空间和编码风格。
这些选项是:
intelephense.diagnostics.undefinedTypes
intelephense.diagnostics.undefinedFunctions
intelephense.diagnostics.undefinedConstants
intelephense.diagnostics.undefinedClassConstants
intelephense.diagnostics.undefinedMethods
intelephense.diagnostics.undefinedProperties
intelephense.diagnostics.undefinedVariables
除了intelephense.diagnostics.undefinedVariables将给出1.2版本的行为外，将所有这些设置为false。查看VSCode设置界面并搜索intelephense。
