Thanks for the PR @DanTheDJ. I just had a couple of comments but need to test this out.

@DanTheDJ I'll get round to a review when I can, pretty busy at the moment with work (and other things, believe it or not) and I'd still like to test this end-to-end.

@DanTheDJ Just getting round to test this e2e but struggling to think about how to set this up on the Unleash side. Working backwards, how are you detecting whether your user should see the toggle in your app?

@DanTheDJ Just getting round to test this e2e but struggling to think about how to set this up on the Unleash side. Working backwards, how are you detecting whether your user should see the toggle in your app?

Hi @mikefrancis The way we have this configured is that we have a feature toggle which can be made available to users by either:

• The tenant/user's plan key (Custom strategy with value passed by the Laravel application during evaluation)
  OR
• The user's ID, allowing manual override for individual users.

Here is the setup on our unleash server:

This means that any of the individual strategies evaluating to true causes the user to see the toggle within the application.

The way this is configured on the Laravel side (running with the PR branch) is as follows:

config/unleash.php

The TenantWithPlanStrategy implements the MikeFrancis\LaravelUnleash\Strategies\Contracts\Strategy interface and returns true if the tenantPlan constraint within Unleash matches.

When the Unleash feature is evaluated, it will check both tenantPlan and userWithId with either one evaluating to true meaning the user sees the toggle as enabled.

Let me know if this clears it up, if not I can provide some further examples

@DanTheDJ Thanks for this.

I'm looking for how you are checking whether to show the feature in your app, are you using Blade, the Feature facade or something else? An example would be great.

@mikefrancis, currently when checking in view files, I have a custom blade directive which then passes through to a helper class I have for tenancy.

In PlanFeatureServiceProvider.php:

Blade::directive('hasFeature', function ($featureCode) {
            return "<?php if (\Domain\Tenancy\Helpers\PlanFeatureHelpers::hasFeatureCode($featureCode)): ?>";
        });

Blade::directive('endHasFeature', function () {
    return '<?php endif; ?>';
});

The helper class just uses the Unleash Facade as follows:

<?php

namespace Domain\Tenancy\Helpers;

use MikeFrancis\LaravelUnleash\Unleash;

class PlanFeatureHelpers {

    static function hasFeatureCode($featureCode)
    {

        $unleash = app(Unleash::class);

        $enabled = $unleash->isFeatureEnabled($featureCode);

        return $enabled;
    
    }

}

I also use this helper around my application to check the eligibility of features via the static method of the Helper, so I guess you could say I only ever use the Unleash facade for my checks.