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
I'm interested in the custom Laravel casts where I propose to thread a docs block as a primary source of type and then use a PHP type. I think that this approach is right, because in case below the docs block have more precise return type than the PHP type.
I know a workaround for this problem where you just need to remove the PHP type but that behavior was unexpected for me when I saw it for the first time.
The change of the approach to threat docs blocks as a primary source of type is a little braking change but at the end of a day we have a better types.
The text was updated successfully, but these errors were encountered:
I'm interested in the custom Laravel casts where I propose to thread a docs block as a primary source of type and then use a PHP type. I think that this approach is right, because in case below the docs block have more precise return type than the PHP type.
Consequently a docs block should looks like below.
I know a workaround for this problem where you just need to remove the PHP type but that behavior was unexpected for me when I saw it for the first time.
Another example can by with the collection.
The change of the approach to threat docs blocks as a primary source of type is a little braking change but at the end of a day we have a better types.
The text was updated successfully, but these errors were encountered: