This is quite hackish, but probably there isn't a better way to handle this.

@markstory Might have ideas. Lets see.

Hello everyone!
I reported the issue in the forums, dereuromark made this PR and asked me to add some more information here instead of forums.

The changes in ComponentRegistry are working like described in documentation. :)

dereuromark mentioned it should be simply possible to register the Component like this:
$container->add(OauthComponent::class);

When doing so, I get the following Exception:

Component App\Controller\Component\OauthComponent is registered in container but cannot be resolved.

For now I am registering the Component like the documentation says:
$container->add(OauthComponent::class) ->addArgument(ComponentRegistry::class) ->addArgument(GenericProvider::class);
and its working.

Thank you!

Another problem I noticed is the following (and I dont know if its because of the cahnges in ComponentRegistry:
If Controller and Component have same names like:

OauthController;
OauthComponent;

I got completely weird results and errors saying:

[Cake\ORM\Exception\MissingTableClassException] Table class for alias Oauth could not be found. in /cakephp/src/ORM/Locator/TableLocator.php on line 249
Exception Attributes: array (
0 => ‘for alias Oauth’,
)

Its weired because I am not using TableLocator anywhere in OauthController or OauthComponent. For now I fixed it changing name of OauthController to something different.

CI failures seem related.