phpinspect can parse the files within a project folder and provide completion for them, but it does not provide completion for any of PHP's built in classes and functions. Such a thing is usually solved with a static index of sorts that can be distributed with an IDE, like an index based on PHPStorm's stubs.
Simply using PHPStorm's stubs to build an index is probably not a good idea with regards to licensing (the derived work would not be GPL as PHPStorm uses apache2 licensing), so this needs to be addressed in a different way.
phpinspect can parse the files within a project folder and provide completion for them, but it does not provide completion for any of PHP's built in classes and functions. Such a thing is usually solved with a static index of sorts that can be distributed with an IDE, like an index based on [PHPStorm's stubs](https://github.com/JetBrains/phpstorm-stubs).
Simply using PHPStorm's stubs to build an index is probably not a good idea with regards to licensing (the derived work would not be GPL as PHPStorm uses apache2 licensing), so this needs to be addressed in a different way.
hugo
added this to the IDE Features milestone 10 months ago
phpinspect can parse the files within a project folder and provide completion for them, but it does not provide completion for any of PHP's built in classes and functions. Such a thing is usually solved with a static index of sorts that can be distributed with an IDE, like an index based on PHPStorm's stubs.
Simply using PHPStorm's stubs to build an index is probably not a good idea with regards to licensing (the derived work would not be GPL as PHPStorm uses apache2 licensing), so this needs to be addressed in a different way.