[FSSDK-10777] update

Author: junaed-optimizely

README.md

@@ -504,8 +504,8 @@ For detailed Next.js examples covering both App Router and Pages Router patterns
 ### Limitations
 
 - **Datafile required** — SSR requires a pre-fetched datafile. Using `sdkKey` alone falls back to a failed decision.
-- **Static user only** — User `Promise` is not supported during SSR.
-- **ODP segments** — ODP audience segments require async I/O and are not available during server rendering. Pass pre-fetched segments via the `qualifiedSegments` prop on `OptimizelyProvider` to enable synchronous ODP-based decisions. Without it, consider deferring the decision to the client using the fallback pattern.
+- **User Promise not supported** — User `Promise` is not supported during SSR.
+- **ODP segments** — ODP audience segments require async I/O and are not available during server rendering. Use [`getQualifiedSegments`](#getqualifiedsegments) to pre-fetch segments server-side and pass them via the `qualifiedSegments` prop on `OptimizelyProvider` to enable synchronous ODP-based decisions. Without it, consider deferring the decision to the client using the fallback pattern.
 
 For more details and workarounds, see the [Next.js Integration Guide — Limitations](docs/nextjs-integration.md#limitations).
 

src/utils.spec.tsx

@@ -235,6 +235,7 @@ describe('utils', () => {
 
     it('returns null when datafile is invalid or missing ODP integration', async () => {
       // undefined datafile
+      // @ts-ignore
       expect(await utils.getQualifiedSegments('user-1')).toBeNull();
       // invalid JSON string
       expect(await utils.getQualifiedSegments('user-1', '{bad json')).toBeNull();

src/utils.ts

@@ -163,7 +163,7 @@ function buildGraphQLQuery(userId: string, segmentsToCheck: string[]): string {
  */
 export async function getQualifiedSegments(
   userId: string,
-  datafile?: string | Record<string, any>
+  datafile: string | Record<string, any>
 ): Promise<string[] | null> {
   let datafileObj: any;