Undefined Functions defined in Drupal .module files?

[drakythe]

I was giving PHPantom a try on PHP Storm using lsp4ij plugin per the README.md instructions. Once I had the path properly pointing to the homebrew bin file it seems to have worked just fine. However I primarily work in Drupal and I'm getting conflicting information once PHPantom is being used, namely that a function doesn't exist. I suspect it is because these function exist inside of .module file in the project and PHPantom just isn't properly parsing that.

Any tips or configuration changes I could make? My knowledge of LSPs is extremely surface level, so this might be a really easy fix that I'm just not aware of how to make.

EDIT: Oh course after I wrote this I finally parsed the README about various indexing strategies and attempted the setup again with a "self" indexing strategy. Still getting flagged that these functions don't exist.

[AJenbo]

Mac or Linux?

I'm getting conflicting information once PHPantom is being used, namely that a function doesn't exist

It just not able to find it or is there conflicting information?

Could you provide something that I can test this on? Even if this is an issue on all possible Drupal setups I would have to learn how to setup a Drupal project to see if I can replicate it.

[drakythe]

@AJenbo My apologies, I'm not yet familiar with Github's discussions setup and I realized I replied not directly to you but to the thread in general.

[drakythe]

MacOS. And apologies for not extrapolating on what I meant by "conflicting" information. Here is a screenshot of what I mean

You'll notice it says "Function not found" and yet it gives me all the information about the function. Maybe this is just some fallback behavior by PHPStorm? I can cmd+click on the function name and it will take me to the function definition as well.

In trying to recreate this behavior in a test project I did discover that the error notification is seemingly temporary. If I open the .module file that holds the function definition and then go back to the tab where the error is displayed and make an arbitrary change (add a new line with $bob = "fred"; for example) the error clears after the autosave processes, as if PHPantom now sees the function (because the file containing it is open) and has reindexed the symbols of my controller file.

The easiest way I know to test this kind of thing is to use DDEV and its CMS Quickstart instructions for Drupal (https://docs.ddev.com/en/stable/users/quickstart/#drupal).

Once I had the DDEV environment started up I did the following steps, without PHPantom enabled:

1. ddev drush generate module to generate a module, being sure to say "Yes" to the question about creating a .module file.
2. ddev drush generate controller and used my test module as the module machien name argument.
3. Opened up the .module file and created my test function. Close the module file
4. Open up the controller file and make a call to my test function. At this point PHP Storm is fine with everything.
5. Enable lsp4ij module, Restart IDE, and add PHPantom to the language servers.
6. Let it process, and issue begins displaying.

This may be a bug, now that I've dug into it more. If you would like me to open an Issue please let me know and I'll do so.

Screenshots of the terminal process below

[AJenbo]

Arh I see, yeah this is sort of a known regression for 0.8.0, I'll try to solve it over the next few days.