dantleech

the pharase `watching with pattern matching LSP file events` in the initialisation message implies that it might not be important for you (Emacs would be responsible for sending the modified...

This looks ok... but it's not clear to me what the problem was? in what way(s) is this an improvement? what concrete benefits are there?

hm, indeed I see! the only potential issue is erasing the original type information (`?object`) if the service cannot be resolved - as that doesn't necessarily mean the service doesn't...

Did you try; ` "indexer.follow_symlinks": true` ? does it work without symlinks?

you can change the root pattern in neovim's LSP config - for example change it to only look for `.phpactor.json` and subsequently ignore that file globally if not already done...

Phpactor uses the following strategies to determine the namespace via. the composer autoloader: https://github.com/phpactor/class-to-file/tree/master/lib/Adapter/Composer - I don't know why it wouldn't work here.

That looks like markdown - and it looks like the hover response. I'd guess you have something configured in regards to hover?

the schema is generated dynamically on composer install: https://github.com/phpactor/phpactor/blob/fba2b766b4e928cb12b49fc942e5029719bf18c2/composer.json#L121-L124 Perhaps the documentation could be updated to show how to generate the schema? or it could be generated in an arbitrary...

No it won't be executed. You can generate it manually, if it's hosted on a website then it would need versioning etc and you'd need to manually match the schema...

would probably make sense to ignore files over a certain size, e.g. 1MB (maybe significantly less) by default. While it would be an improvement to have the indexer in a...