Report deprecations as warnings instead of errors

[nesk]

I think using a deprecated class/method/property/whatever (let's name those as entity) shouldn't be reported as an error but as a warning. The key differences I see here are:

• The code using a deprecated entity will run, it just might break one day, but PHPStan will then trigger an error about the entity being unknown.
• Reporting a warning instead of an error should not make the CLI exit with a status code different than 0, but it should still output the deprecation message.

Sometimes I deprecate some classes/methods in my code until I'm sure I don't use them anymore, however PHPStan will then complain about them, so I must ignore the errors, which defeats the purpose of using those deprecation rules.

What do you think about this?

[iluuu1994]

There are no warnings in PHPStan right now. Everything is treated as an error. So this would first have to be implemented in PHPStan itself.

[ondrejmirtes]

And I don’t think it’s necessary. You can do multiple things today to achieve what you want:

• Ignore those deprecation errors you don’t want to see using ignoreErrors.
• Run deprecation-rules via separate PHPStan config.
• Install and uninstall deprecation-rules only when you want to see them.

[iluuu1994]

I don't think it would be awfully useful either. The difference between a warning and an ignored error would be that it's still displayed. But you only really care about the warnings when you try to solve them. They also make it more difficult to see the actual errors.

Maybe it's better to ignore the errors and add them to your task list to fix for the next release?

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.