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
{{ message }}
This repository has been archived by the owner on Mar 29, 2024. It is now read-only.
Some methods , e.g. Script::run() may return any of Value types and it comes in handy when IDE could typehint them. There are other methods which offers rich return type variation. As I personally use PhpStorm and it's pretty decent IDE, I'd like to give it first-class support and make more developers happy.
The text was updated successfully, but these errors were encountered:
It looks like PhpStorm advanced metadata is not designed to solve this problem yet.
Anyway, the user is responsible to check what value type/king he's receiving and do not depend on suggestions to keep pita low. While I'd really like to add this feature, it's not feasible at the moment and there is no clear roadmap how to achieve that. Bloating @return type with all possible subtypes is not the best idea.
https://confluence.jetbrains.com/display/PhpStorm/PhpStorm+Advanced+Metadata
Some methods , e.g.
Script::run()
may return any ofValue
types and it comes in handy when IDE could typehint them. There are other methods which offers rich return type variation. As I personally use PhpStorm and it's pretty decent IDE, I'd like to give it first-class support and make more developers happy.The text was updated successfully, but these errors were encountered: