feat: MetaStorm integration

[xepozz]

MetaStorm integration.
Start integrating MetaStorm:

• xepozz/meta-storm-idea-plugin
• PHPStorm Marketplace

Found a few more additional features that must be integrated to make Symfony more developer friendly. It's not replacement for Symfony PHPStorm Plugin, at least for now.

Let me know if you're interested in further MetaStorm integration.
Thanks for any feedback.

Here are a few screenshots what the .meta-storm.xml already made with the demo project.

[xabbuh]

Can you elaborate a bit on the advantage of using your plugin that requires a custom config compared to the Symfony plugin?

[xepozz]

Hi @xabbuh
Thanks for the question. I've added a few points I recon important:

https://github.com/xepozz/meta-storm-idea-plugin?tab=readme-ov-file#advantages

Advantages

No need dedicated IDE plugin to support your own framework
Anyone can extend or override plugin functionality
So if a feature is not ready by the dedicated IDE plugin, MetaStorm is ready to covers with its possibilities
No need to support legacy codebase in the dedicated IDE plugin
Written component config might be used with any other projects, like Symfony Console and almost the whole PHP world
Life save for single developers, any library configuration might improve developer experience with less knowledge
Totally free

[stof]

This explains the benefits for projects that don't have a plugin specific to their framework. But the Symfony plugin exists since years. So what are the benefits for a Symfony project compared to using the Symfony plugin (which does not require any config) ?

[xepozz]

Seems like the author isn't ready to support the plugin further, but I don't want to talk about it.

So what are the benefits for a Symfony project compared to using the Symfony plugin (which does not require any config) ?

MetaStorm is not a replacement for any dedicated software plugins because it serves a general-purpose role.

Many Symfony components are used outside of the Symfony skeleton, demo, or template applications. As a result, not all projects may use the Symfony Plugin, even though they rely heavily on Symfony components.

The main goal of MetaStorm is to provide library developers with a way to integrate their software, making it reusable within different codebases.

MetaStorm can be used alongside the Symfony Plugin or independently. My goal is to improve the UX/DX as much as possible by integrating helpful functions into projects and enabling maintainers to define how it should be properly configured.

MetaStorm works with any configuration files it can locate. For example, I could create the xepozz/metastorm-symfony package with just one .meta-storm.xml file, but that would likely confuse users, wouldn’t it?

Additionally, I addressed the feature request with a few lines of code: Haehnchen/idea-php-symfony2-plugin#2410.

If you disagree with this proposal, I’m happy to close it.

This version is more polished and professional. Let me know if you’d like further refinements!