Add information about alternatives

My friend, this is a two way process. Please do your share first. 🙂

My friend of course I added alternatives - here you can see them → .

The only issue I see is that this module should be deprecated in favor of native drush phpstorm-meta because it provides much deeper integration with phpstorm, you can check all templates that they provide here.

Thank you!

In project the description you say:

Native drush command - phpstorm-meta

but this is no native Drush command. Native Drush commands are included into Drush core. But the drush phpstorm-metadata:generate comes from the PhpStorm Metadata module.

Please add a link to PhpStorm Metadata module and a description of what it does and how it's different from your plugin. Please also update the README of the plugin.

About the deprecation, I disagree. I still see use-cases for an actual Drupal module over a plugin:

PhpStorm Metadata can simply be added into a project via Composer and executed via Drush in a setup script which is good DX for when you expect somebody to quickstart with a project without needing to configure PhpStorm first.

> About the deprecation, I disagree. I still see use-cases for an actual Drupal module over a plugin:

I didn't mean to deprecate module over plugin. I meant to deprecate plugin over native drush generate phpstorm-meta that has much deeper integration with PHPStorm since they provide support for routes, roles, services, settings, states, fields, field definitions, entity_types, date formates, configuration and more. You can see all the things that they provide here. Just run drush generate phpstorm-meta and you will see every file it generates. Drush depends on Chi-teck/drupal-code-generator, that provides all templates for drush generate command.

Ahaaaa, I see. I didn't know this exists!

You definitely need to fix the README and the project page to print the right command, because neither drush generate-metadata nor drush phpstorm-meta.

It's as you wrote here correctly drush generate phpstorm-meta.

Yes, we should deprecate the module over the native generate command then.

Automatically closed - issue fixed for 2 weeks with no activity.