PhpDoc | PhpDoc support package | Autocomplete library

The short answer is no.

My understanding is that enforcing such a thing has terrible performance problems. Some people want to go all the way and have full blown generics, others just want type-safe collections. Some people worry that implementing the latter first might hinder the development of the former. So we’re at a standstill.

There’s the occasional discussion in the community such as this: https://externals.io/message/108175

You can't do that using comments or other in-editor features, but you can add them to "Ignored Files and Folders" list at File | Settings (Preferences on Mac) | Editor | File Types, if they have some common naming pattern.

See also https://www.jetbrains.com/help/phpstorm/creating-and-registering-file-types.html#ignore-files-folders

You can include the phpDoc generation within your CI/CD script:

first install the phpDocumentor on the production, then generate using this command:

I believe you have misunderstood what Attributes are for, and how they related to doc blocks. There are two common uses of doc blocks (comments marked with /** ... */):

• To document the code (hence the name "doc block"), in a mostly-standardised way which can be read by various tools, including documentation generators and IDEs.
• To add machine-readable annotations to the code, for use with libraries and frameworks that can automatically generate behaviour based on those. For instance, an ORM might use an annotation of @TableName('Foo') to link a class to a particular database table, and generate appropriate SQL.

The example you've shown is of the first usage. What you have written is still the correct way of writing documentation.

PHP 8's native Attributes replace the second usage. It's up to the library what Attributes to look for, but an ORM that previously looked for @TableName('Foo') in a docblock might now look for #[TableName('Foo')] as a native Attribute instead.

The @template annotation relates to a concept called Generics, which does not currently exist in PHP, but are a way of dynamically describing the contents of a parameter or return type that would be unknown until a class is instantiated or method called.

For PHP specifically, here is an article describing the doc blocks themselves and how to use them.

For the code you referenced, the template specifies T will be an instance of Extension\Extension. The $id parameter will be the class name for T, and @return says the method will return an instance of T.

Using the method would be something like $faker->ext(MyExtension::class), which would return an instance of MyExtension.

If you want to follow the rabbit, here is more on Generic Programming.

in some cases you can if you are you using js files you need to create a jsconfig.json at the root of your project

Technically it will not make a big difference. But if you're using PHP 7 or higher, you can mention return type in the code itself rather than in the comment. It'll help you, IDE, and the compiler to understand what to expect and your code will be protected from dynamic returns. So instead of doing,

install the extension PHP Extension Pack and PHP IntelliSense, also if you like to check for bug you will need to set you path to your php.exe in your setting.json example

First of all, the ? goes before the type, not after... other than this:

Using