optimizely-exp-implementation

Optimizely Implementation Agent

Analyze SDK implementation patterns, initialization, and configuration.

Analysis Areas

1. SDK Initialization

IMPL-001: SDK Initialized Without Datafile (Critical)

SDK must have datafile access:

Grep: createInstance\s*\(\s*\{(?!.*datafile)(?!.*sdkKey)

Bad Pattern:

// Missing datafile configuration!
const optimizely = optimizelySdk.createInstance({
  // No sdkKey or datafile
});

Good Pattern:

const optimizely = optimizelySdk.createInstance({
  sdkKey: process.env.OPTIMIZELY_SDK_KEY,
  datafileOptions: {
    autoUpdate: true,
    updateInterval: 60000,
  },
});

2. Blocking Initialization

IMPL-002: Blocking SDK Initialization (Critical)

SDK initialization should not block rendering:

Grep: await.*createInstance
Grep: \.then\(.*createInstance
Grep: optimizely.*=.*await

Bad Pattern:

// Blocks page load!
const optimizely = await optimizelySdk.createInstance({
  sdkKey: SDK_KEY,
});
// Nothing renders until SDK is ready

Good Pattern:

// Non-blocking with ready handler
const optimizely = optimizelySdk.createInstance({
  sdkKey: SDK_KEY,
});

optimizely.onReady().then(() => {
  // SDK is ready, but page already rendered
});

Best Pattern (React):

<OptimizelyProvider
  optimizely={optimizely}
  timeout={500}  // Max wait time
>
  <App />
</OptimizelyProvider>

3. Error Handling

IMPL-003: No Error Handling for Decisions (Warning)

Decisions should have error handling:

Grep: decide\(.*\)(?!.*catch)
Grep: isFeatureEnabled\(.*\)(?!.*\?\?)

Bad Pattern:

// No error handling - will throw on SDK errors
const decision = optimizely.decide('feature_key');
const isEnabled = decision.enabled;

Good Pattern:

try {
  const decision = optimizely.decide('feature_key');
  return decision.enabled;
} catch (error) {
  console.error('Optimizely decision error:', error);
  return false; // Safe default
}