You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Was just trying out padawan.php + deoplete, and realized my symfony project is unable to autocomplete some basic stuff.
Dug around with it and found this:
Moreover, when trying to edit the inside of a sneakyTraitFunction(), some stuff seems to break.
POST /complete
[2017-11-22 05:00:39] completer.INFO: Traversing with 1 walkers [] []
[2017-11-22 05:00:39] completer.DEBUG: Processing 1 classes [] []
[2017-11-22 05:00:39] completer.DEBUG: Processing 0 interfaces [] []
[2017-11-22 05:00:39] completer.DEBUG: Processing 0 functions [] []
[2017-11-22 05:00:39] completer.DEBUG: Processing node Traitor [] []
[2017-11-22 05:00:39] completer.INFO: Traversing with 1 walkers [] []
Unhandled error: Argument 1 passed to Padawan\Framework\Domain\Project\InMemoryIndex::findClassByFQCN() must be an instance of Padawan\Domain\Project\FQCN, instance of Padawan\Domain\Project\FQN
given, called in /home/reafle/dotfiles/vim/plugged/deoplete-padawan/vendor/mkusher/padawan/src/Padawan/Parser/Walker/ScopeWalker.php on line 172
POST /complete
[2017-11-22 05:00:42] completer.INFO: Traversing with 2 walkers [] []
Unhandled error: Argument 3 passed to Padawan\Framework\Generator\IndexGenerator::processFileScope() must be an instance of Padawan\Domain\Scope\FileScope, array given, called in /home/reafle/do
tfiles/vim/plugged/deoplete-padawan/vendor/mkusher/padawan/src/Padawan/Framework/Complete/CompleteEngine.php on line 142
Am I doing something wrong, or this is a bug?
The text was updated successfully, but these errors were encountered:
Was just trying out padawan.php + deoplete, and realized my symfony project is unable to autocomplete some basic stuff.
Dug around with it and found this:
Moreover, when trying to edit the inside of a
sneakyTraitFunction()
, some stuff seems to break.Am I doing something wrong, or this is a bug?
The text was updated successfully, but these errors were encountered: