is PreventAccessFromUnwantedDomains useful when InitializeTenancyByRequestData is used?

[nikola-maric-aula]

Hi i'm starting to use your project v4 and I stumbled upon a couple of inconsistencies, or maybe I'm just misunderstanding something.. Let me know if you'd welcome a PR to address my uncertainties.

Why would we want to high-prio init PreventAccessFromUnwantedDomains if we're only using InitializeTenancyByRequestData?

tenancy/assets/TenancyServiceProvider.stub.php

Line 252 in 0cd0bc4

$tenancyMiddleware = array_merge([Middleware\PreventAccessFromUnwantedDomains::class], config('tenancy.identification.middleware'));

It also seems UsableWithEarlyIdentification->shouldBeSkipped() is checking for Tenancy::routeIsUniversal($route), so here the second condition is not necessary?

tenancy/src/Middleware/PreventAccessFromUnwantedDomains.php

Line 34 in 0cd0bc4

if ($this->shouldBeSkipped($route) || tenancy()->routeIsUniversal($route)) {

[stancl]

1. It's just priority, it has no effect when the middleware isn't used. Similarly, InitializeTenancyByRequestData itself has a high priority set even if you only use domain identification.
2. Think that's because shouldBeSkipped() is checking for other things alongside Tenancy::routeIsUniversal. Tests do not fail if || tenancy()->routeIsUniversal($route) is removed, though I'm not sure if that's due to tests not catching some edge case or if the check is indeed redundant. Will take a look.