When we can expect laravel/framework package to have return types build in?

[mikield]

It's 2024, and PHP 8.4 has been released.

Strong typed codebases have been proven stability over non strong typed code.

I am asking myself, when we can see such big tool as Laravel that's used by billions of web apps to be strong typed?!

Do Laravel team has some plans on it?
If yes - I would like to contribute :)

[ghost]

Never:)

[mikield]

Do only me feels like we need here an RuntimeException?
Like, if you expect your code not to run - throw new Exception that will allow user to catch it and write "catch" case code.

[mikield]

@marius-mcp I am coding only laravel for like 6+ years now, so I can not say that I do not like it, I want the best for the tool that I like :)

But I understand your point, Laravel is kinda Apple from PHP dev for some people :)

[ghost]

@mikield good thing is that the packages for laravel can be written ~ 90% with return types and typed params. Also the projects that we build using laravel/lumen.

[puklipo]

There is precedent for very painful breaking changes destroying communities.
The only solution is to introduce types little by little with each major version upgrade.
Newer packages that don't need to worry about breaking changes are well-typed.

[ghost]

@puklipo that is why I said never. At first I thought it is possible, but after more than 3 years working with it, I understood it is not possible because of the backward compatibility issues..

[macropay-solutions]

The reason it Returns Eloquent builder instead of int: #56664

[macropay-solutions]

@mikield we started applying PSR12 but we did not touch the return types or the parameters types.