Currently StreamWrapperManager has addStreamWrapper, register() and unregister() documented as
*
* Internal use only.
*without the @internal flag.
These functions are necessary for Core to bootstrap however they are generally not necessary for most modules likely justifying them generally being considered internal.
However since the StreamWrapperManager is a Drupal Service it is possible to decorate with a Service Decorator. Any module wanting to decorate the StreamWrapperManager must implement these methods or core will be unable to function.
Possible reasons to Decorate the StreamWrapperManager service that I have seen are:
With these functions not on the interface they appear (by policy) to be subject to change in minor point releases without any deprecation window making decorating the service appear 'risky'.
See core/lib/Drupal/Core/StreamWrapper/StreamWrapperManager.php
Add addStreamWrapper, register(), unregister() to a new interface.
Document they are generally not to be called and are on interface solely for Drupal Core and Service Decorators.
None
New interface created for existing methods.
None Expected.
TBD
Needs work
10.1 ✨
Last updated
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
This could use a test case to show the issue.