markdown guide
 

I mean, Java has had return types and all that good stuff for much longer than PHP--obviously--and Javadoc is still a thing, so....

 

I'd say there's still a place. Type info only goes so far and PHPDoc is more than just type information!

I work with Drupal on occasion and deal with PHPDoc-driven documentation like api.drupal.org/api/drupal/core%21l...

I would not want to try to deal with the number of distinct classes it would take to express that same level of information. I'm not sure it's realistically possible.

 

I would gladly welcome a PHPDoc flavour (or IDE configuration option) where you don't have to provide parameters or return value types. Unfortunately sometimes you have to provide it when you want to document type of array values.

 
 

No PHPDoc is still relevant. Documentation is key to the best code ever written. PHPDocs provide you with another level of documentation that is useful in source code.

Classic DEV Post from Mar 6

GraphQL performance issues & an easy solution

One of the biggest GraphQL flaws is missing of some basic implementations know from REST which are crucial for application performance.

James King profile image

Read more long-form software content.

Sign up (for free)

Become a better software developer.