document service tags for service interfaces

daniel.j → made their first commit to this issue’s fork.

I've created a fork and branch for this work and pushed changes inline with what jochim suggested.

Currently, I've only added to the docs of 'service_collector' tags in the 'commerce_order' module. I plan to continue to add this documentation in this style to the other modules and declared services.

Please let me know if this change is no longer desired / if a different approach would be better.

I've added this line of documentation to each of the other services in the commerce core and sub-module services in the '2914933-document-service-tags-service-interfaces' branch, but not made a MR.

It would be great if this could be reviewed. Is this change still desired? Should it be done in a different way? Thanks!

@daniel.j: Not sure where your changes can be reviewed? This is the repo to use for the documentation: https://github.com/centarro/commerce-docs.

@jsacksick Apologies if I've misunderstood, I mean the addition to of the class docs rather than the commerce documentation.

I've openned a MR for review (https://git.drupalcode.org/project/commerce/-/merge_requests/357), however the composer step of the pipeline is failing.

Because your MR needs to be against the 3.0.x branch, not 8.x-2.x.

daniel.j → closed merge request !357

daniel.j → changed the visibility of the branch 3.0.x to hidden.

Thanks! Now a new merge request targeting 3.0.x, hopfully this looks better.

@daniel.j: Thanks! Merged!

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