find_use expand_fqcn and goto_definition_scope don't work

[thatdoorsajar]

I have closed sublime deleted index, opened sublime and run the GoTo Project Symbols which has reindexed sublime successfully. find_use expand_fqcn and goto_definition_scope are still not working on any assigned key combo or through running the commands from the Command Palette.

import_namespace and insert_php_constructor_property work as expected so the package is working.

find_use and expand_fqcn don't have any output in the console or bottom bar when they are run.

goto_definition_scope has no output in the console but it does say "Unable to find {ClassName}" in the bottom bar when run.

I was successfully running this package on a different machine but this new one no luck! Any suggestions?

[elboletaire]

Same here, using latest dev build (which right now is 3113)

[jleger98]

Ditto. Same issue, using ST3 v3114 and latest from PC.

[hughsaffar]

Did anyone found a workaround?

[thatdoorsajar]

@hughsaffar not for me atm

[iamanders]

Same problem here, with build 3113

[iamanders]

I did some digging around in the code. Seems like the row below is always returning an empty array, even when hardcoded a symbol that exists in my project.

files = window.lookup_symbol_in_index(symbol)

https://github.com/erichard/SublimePHPCompanion/blob/master/php_companion/utils.py#L18

Is this a Sublime bug maybe? This is above my Sublime skills, otherwise I would do a PR.

EDIT:
Maybe related to this?
sublimehq/Packages#410

[erichard]

Sorry guys For not replying here. I just don't see what I can do as I can't reproduce the problem on my machine.

As @iamanders say, it could be a Sublime bug with the index engine. Hopefully the next build will fix this.

[leandromatos]

It's too bad work without this feature, it has saved me a good time.

[iamanders]

Just upgraded to the last beta build (3118) and the problem remains.

[erichard]

Maybe an issue is referenced in sublime core issue tracker. Please take a look at https://github.com/SublimeTextIssues/Core

[elboletaire]

It works for me now, using 3118 under both Windows and Linux :\

[iamanders]

Thats weird, works for me too now! Same version (3118) as my last comment. Don't think I have made any config changes, or installed/removed any plugins since then. Really happy that it's working now.

[elboletaire]

Same here, it was not working yesterday. It works today... really weird.

[thatdoorsajar]

This seemed to be an issue with Sublime Text core. Now working in Sublime Text Dev Build 3118 - https://www.sublimetext.com/3dev