Weave Code
PHP implementation of the OpenFeature SDK
Frequently asked questions about Sdk
- How do I integrate OpenFeature SDK with Laravel’s service container for dependency injection?
- Use a Laravel service provider to bind `OpenFeatureAPI` as a singleton in the container. For example, register a provider that initializes the API with your preferred provider (e.g., `FlagdProvider` or `LaunchDarklyProvider`). This allows Laravel’s DI system to inject the client anywhere in your application.
- Which Laravel versions does the OpenFeature PHP SDK support?
- The SDK itself requires PHP 8.0+, but it integrates with any Laravel version supporting PHP 8.0+. Tested configurations include Laravel 8.x, 9.x, and 10.x. Ensure your Laravel app meets the PHP version requirement, and the SDK will work seamlessly with Laravel’s service container and middleware.
- Can I use multiple feature flag providers (e.g., LaunchDarkly + Flagsmith) with this SDK?
- Yes, the SDK supports multi-provider setups, but named clients (to switch providers dynamically) are not yet implemented. You can manually swap providers via the container or use middleware to route requests to different providers based on context. Track issue #93 for updates on named clients.
- How do I inject user-specific context (e.g., user ID, roles) into flag evaluations?
- Use Laravel middleware to set the evaluation context before flag checks. For example, create middleware that injects user attributes (e.g., `user()->id`) into an `EvaluationContext` object. This ensures flags are evaluated with the correct user or request-specific data.
- What’s the best way to mock OpenFeature flags in Laravel tests?
- Use Laravel’s mocking capabilities or the `NoOpProvider` for isolated testing. Bind a mock provider in your test service container to return predefined flag values. For example, replace the real provider with a test double that ignores remote calls and returns hardcoded responses.
- Does the SDK support caching flag evaluations for performance?
- The SDK itself doesn’t include caching, but you can integrate Laravel’s cache facade to store frequent flag evaluations. For example, cache the result of `getBooleanValue()` for a given flag key and context. This reduces latency and provider load, especially for high-traffic applications.
- How do I use OpenFeature flags in Laravel Blade templates?
- Create a Blade directive to simplify flag checks. For example, register a directive like `@feature('flag_key')` that resolves to `true` or `false` using the OpenFeature client. This keeps your views clean while leveraging dynamic feature toggles.
- What happens if the remote feature flag provider fails (e.g., network error)?
- Configure fallback behavior by setting default values in your provider or using a local cache. The SDK allows you to define fallback logic, such as returning a cached value or a hardcoded default. Ensure your provider implements graceful degradation for resilience.
- Are there alternatives to OpenFeature for Laravel feature flagging?
- Yes, alternatives include vendor-specific SDKs like LaunchDarkly’s PHP SDK or Flagsmith’s Laravel package. However, OpenFeature provides a unified API across providers, making it easier to switch tools without rewriting flag logic. It’s ideal for teams using multiple providers or planning future-proofing.
- How do I monitor flag usage or evaluation metrics in production?
- Use OpenFeature’s hooks to log evaluations or integrate with Laravel’s telemetry tools. For example, create a custom hook to track flag keys, contexts, and results in a database or monitoring system. Third-party APM tools like New Relic can also capture flag-related metrics.
Weaver
How can I help you explore Laravel packages today?