I will add the administration files, the changelog file and tests within the next few days.

Codecov Report

Attention: Patch coverage is 0% with 140 lines in your changes missing coverage. Please review.

Project coverage is 43.83%. Comparing base (21cee05) to head (6904b1d).
Report is 10110 commits behind head on trunk.

@@             Coverage Diff             @@
##            trunk    #5362       +/-   ##
===========================================
- Coverage   65.46%   43.83%   -21.64%     
===========================================
  Files        3677     3081      -596     
  Lines       82789    87693     +4904     
===========================================
- Hits        54201    38439    -15762     
- Misses      28588    49254    +20666     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Hey @M-arcus, what is the state of this PR? Are you currently working on it?

In general we think this feature would be best served as an extension and not in the core framework, so if you do plan on continuing to work on it, please ping so we can discuss. We appreciate the effort and wouldn't want to disappoint any one involved, so we should communicate and make sure we are all on the same page! That does not mean we say no: but we should definitely discuss and weigh up the advantages/disadvantages of this living in the framework 😄

@AydinHassan

what is the state of this PR?

It is technically complete, but needs tests and admin components.

Are you currently working on it?

Yes, I am still working on this, but wasn't able to finish it due to time constraints and workload.

In general we think this feature would be best served as an extension and not in the core framework

What speaks against including it as a core feature? It was a core feature in Shopware 5 and helped integrators and agencies a lot when identifying modifications on the code.

@M-arcus in general for us, the question is rather: why does it need to be in core?

A few points we discussed:

• We will have to maintain this feature that we did not build. You and the others involved are better placed to maintain it, you are experienced in the area and understand the problem and solution space. You can argue it's a simple feature but we are a small team and Shopware has many thousands of simple features and of course many complex ones.
• It's only useful for a small subset of our users/customers
• You are restricted to the platform release schedule

We don't doubt it's absolutely useful, but we're not convinced it should be in core. From our perspective it would be better as an extension. And not just better for us in terms of maintenance load, it's better for you and the ecosystem because you can iterate as you please.

Is there something special you cannot do as an extension?

@AydinHassan
In my opinion the best place for this functionality is within the core because it would provide a quick way to diagnose non-standard code changes, but I agree, that the target audience is rather small, since it would only affect plugin creators debugging during support requests.

I will move the code from this PR to a PR in https://github.com/FriendsOfShopware/FroshTools as a similar functionality already exists there, but only for changes in the core.

@M-arcus thanks for understanding!