-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to change phpstan rule level #28
Comments
I've personally never feel the need for it (IDE is not like CI as there's no binary result, and marking any suspicious may be useful) but I see how this can be distracting - I'll put it in the next iteration. |
what about config files for phpstan, it does not seem to pick up my config: phpstan.neon, but I might be mistaking |
Indeed,
Phpstan levels are pretty stable in general so it may be useful to pick them from |
That is unfortunate, since I am using Laravel. I also use the config from https://github.com/nunomaduro/ with phpstan vs code plugin to better match Laravel logic, but since your plugin support phpstan + other awesomeness, it would make sense me to only use that instead of phpstan vs code plugin. But right now I get way too many errors with your plugin because the neon file is not supported. |
@tsufeki |
I agree with @crissi, your plugin would be awesome if it supported Larastan (https://github.com/nunomaduro/larastan). Maybe it's a good idea to open a separate issue for it? |
Is it possible to analyse codebase with stan using
--level
argument? In many other editor extensions there is such option, but this awesome ls lacks it.The text was updated successfully, but these errors were encountered: