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
Forgive me if I'misunderstanding the intended power of stubs, but I come from phpstan where stubs are just used for changing docblocks 😃. We've run into this over at psalm/psalm-plugin-laravel#21
interface UserContract {}
class User implements UserContract {}
And then a stubfile for user like the following, which was intended to add documentation to the User class:
/*** @property string $name*/class User {}
Since the stub file doesn't have the interface listed, psalm thinks the User class no longer satisfies the UserContract. Is this intentional behavior? I found #482, which makes me thing that this might be a bug
The text was updated successfully, but these errors were encountered:
Hello!
Forgive me if I'misunderstanding the intended power of stubs, but I come from phpstan where stubs are just used for changing docblocks 😃. We've run into this over at psalm/psalm-plugin-laravel#21
And then a stubfile for user like the following, which was intended to add documentation to the
User
class:Since the stub file doesn't have the interface listed, psalm thinks the
User
class no longer satisfies theUserContract
. Is this intentional behavior? I found #482, which makes me thing that this might be a bugThe text was updated successfully, but these errors were encountered: