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
However I'm not very familiar with these tools and I'm not sure if the result is useable with intelephense. The resulting stubs file is over 9MB (perhaps there are ways to optimize and reduce the size?).
I have tried placing the stubs file in the root folder of my VSCode project, I have also tried adding the stubs file to a mediawiki stubs folder in the extension's node_modules, and adding mediawiki to the package.json list of intelephense stubs, then enabling mediawiki in the extension settings for stubs. However I'm still getting red underlines on all Mediawiki classes and methods, so I'm not sure what I'm not doing correctly.
In any case, if anyone more experienced is willing to generate Mediawiki stubs and include them in the intelephense extension, this would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I have made an attempt at generating Mediawiki stubs using
nikic/php-parser
: https://github.com/JohnRDOrazio/mediawiki-stubsHowever I'm not very familiar with these tools and I'm not sure if the result is useable with intelephense. The resulting stubs file is over 9MB (perhaps there are ways to optimize and reduce the size?).
I have tried placing the stubs file in the root folder of my VSCode project, I have also tried adding the stubs file to a
mediawiki
stubs folder in the extension'snode_modules
, and addingmediawiki
to the package.json list of intelephense stubs, then enablingmediawiki
in the extension settings for stubs. However I'm still getting red underlines on all Mediawiki classes and methods, so I'm not sure what I'm not doing correctly.In any case, if anyone more experienced is willing to generate Mediawiki stubs and include them in the intelephense extension, this would be greatly appreciated.
The text was updated successfully, but these errors were encountered: