@salesforce/webapp-template-feature-react-authentication-experimental 1.105.0 → 1.106.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-feature-react-authentication-experimental",
-  "version": "1.105.0",
+  "version": "1.106.0",
   "description": "Authentication feature for web applications",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",
@@ -16,7 +16,7 @@
     "clean": "rm -rf dist"
   },
   "devDependencies": {
-    "@salesforce/webapp-experimental": "^1.105.0",
+    "@salesforce/webapp-experimental": "^1.106.0",
     "@tanstack/react-form": "^1.27.7",
     "@types/react": "^19.2.7",
     "@types/react-dom": "^19.2.3",

package/dist/.a4drules/features/feature-graphql-graphql-data-access-rule.md

@@ -1,470 +0,0 @@
----
-paths:
-  - "**/*.ts"
-  - "**/*.tsx"
----
-
-# GraphQL Data Access
-
-Instructs agents to use the established GraphQL utilities for Salesforce data access.
-
-## TypeScript Types & Code Generation
-
-### Generated Types File
-
-Types are auto-generated at: `src/api/graphql-operations-types.ts`
-
-### Generation Command
-
-```bash
-npm run graphql:codegen
-```
-
-The codegen configuration is at `codegen.yml` and generates types from:
-
-- Schema: `schema.graphql` (project root)
-- Documents: `src/**/*.{graphql,ts,tsx}`
-
-### Type Naming Convention
-
-For a GraphQL operation named `GetHighRevenueAccounts`:
-
-- **Query/Mutation Response Type**: `GetHighRevenueAccountsQuery` or `GetHighRevenueAccountsMutation`
-- **Input Variables Type**: `GetHighRevenueAccountsQueryVariables` or `GetHighRevenueAccountsMutationVariables`
-
-## Core Types & Function Signatures
-
-### getDataSDK Function
-
-Available from `@salesforce/sdk-data`:
-
-```typescript
-import { getDataSDK } from "@salesforce/sdk-data";
-
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType, VariablesType>(query, variables);
-```
-
-`getDataSDK()` returns a lazily-initialized `DataSDK` singleton. The `graphql` method uses optional chaining (`?.`) because not all surfaces support GraphQL.
-
-### gql Template Tag
-
-Also available from `@salesforce/sdk-data` for inline query definitions:
-
-```typescript
-import { gql } from "@salesforce/sdk-data";
-
-const MY_QUERY = gql`
-  query MyQuery {
-    uiapi {
-      ...
-    }
-  }
-`;
-```
-
-The `gql` tag is a template literal that allows defining GraphQL queries inline while maintaining syntax highlighting in most editors.
-
-### GraphQLResponse Shape
-
-`data.graphql?.()` returns `GraphQLResponse<T>`. Callers destructure `{ data, errors }` and handle errors themselves:
-
-```typescript
-interface GraphQLResponse<T> {
-  data: T;
-  errors?: Array<{
-    message: string;
-    locations?: Array<{ line: number; column: number }>;
-    path?: string[];
-  }>;
-}
-```
-
-### Handling Mixed Responses (Partial Success)
-
-GraphQL can return **both `data` and `errors`** in the same response (partial success). For example, some fields may resolve while others fail due to field-level security. Choose a strategy per use case:
-
-```typescript
-// Strategy A: Strict — treat any errors as failure (default for most queries)
-if (response?.errors?.length) {
-  throw new Error(response.errors.map((e) => e.message).join("; "));
-}
-const result = response?.data;
-
-// Strategy B: Tolerant — log errors but use partial data
-if (response?.errors?.length) {
-  console.warn("GraphQL partial errors:", response.errors);
-}
-const result = response?.data;
-
-// Strategy C: Discriminated — fail only when no data came back
-if (response?.errors?.length && !response?.data) {
-  throw new Error(response.errors.map((e) => e.message).join("; "));
-}
-if (response?.errors?.length) {
-  console.warn("Partial success with errors:", response.errors);
-}
-const result = response?.data;
-```
-
-**When to use each:**
-
-- **Strategy A** — Default. Use for queries where incomplete data would be misleading (e.g., financial summaries, approval workflows).
-- **Strategy B** — Use when partial data is still useful and the UI can degrade gracefully (e.g., dashboard tiles, optional fields).
-- **Strategy C** — Use for mutations where the operation may succeed but some return fields are inaccessible.
-
-For mutation-specific partial responses, see `docs/generate-mutation-query.md` which covers `PARTIAL` and `FAILED` status handling workflows.
-
-### NodeOfConnection Utility Type
-
-Extract the node type from a connection (edges/node pattern):
-
-```typescript
-import { type NodeOfConnection } from "@salesforce/sdk-data";
-
-// Extract Account node type from the query response
-type AccountNode = NodeOfConnection<GetHighRevenueAccountsQuery["uiapi"]["query"]["Account"]>;
-```
-
-### UIAPI Response Shape
-
-All Salesforce GraphQL record queries follow this structure (https://developer.salesforce.com/docs/platform/graphql/guide/query-record-objects.html):
-
-```typescript
-interface UIAPIQueryResponse {
-  uiapi: {
-    query: {
-      [ObjectName]: {
-        edges?: Array<{
-          node?: {
-            Id: string;
-            [FieldName]?: { value?: FieldType | null } | null;
-            // Reference fields include the related record
-            [ReferenceField]?: {
-              value?: string | null; // The ID
-              [RelatedField]?: { value?: RelatedType | null } | null;
-            } | null;
-          } | null;
-        } | null> | null;
-      } | null;
-    };
-  };
-}
-```
-
-## Required Workflow
-
-There are **two acceptable patterns** for defining GraphQL queries:
-
-### Pattern 1: External .graphql File (Recommended for complex queries)
-
-#### Step 1: Create .graphql File
-
-Store queries in `.graphql` files for codegen to process:
-
-```graphql
-# src/api/utils/query/myQuery.graphql
-query GetMyData($myVariable: String) {
-  uiapi {
-    query {
-      MyObject(first: 10, where: { Field: { eq: $myVariable } }) {
-        edges {
-          node {
-            Id
-            Name {
-              value
-            }
-          }
-        }
-      }
-    }
-  }
-}
-```
-
-#### Step 2: Run Code Generation
-
-```bash
-npm run graphql:codegen
-```
-
-This generates types in `graphql-operations-types.ts`:
-
-- `GetMyDataQuery` - response type
-- `GetMyDataQueryVariables` - variables type
-
-#### Step 3: Import and Use
-
-```typescript
-import { getDataSDK, type NodeOfConnection } from "@salesforce/sdk-data";
-import MY_QUERY from "./query/myQuery.graphql?raw";
-import type { GetMyDataQuery, GetMyDataQueryVariables } from "../graphql-operations-types";
-
-type MyNode = NodeOfConnection<GetMyDataQuery["uiapi"]["query"]["MyObject"]>;
-
-export async function getMyData(variables: GetMyDataQueryVariables): Promise<MyNode[]> {
-  const data = await getDataSDK();
-  const response = await data.graphql?.<GetMyDataQuery, GetMyDataQueryVariables>(
-    MY_QUERY,
-    variables,
-  );
-
-  if (response?.errors?.length) {
-    const errorMessages = response.errors.map((e) => e.message).join("; ");
-    throw new Error(`GraphQL Error: ${errorMessages}`);
-  }
-
-  return response?.data?.uiapi?.query?.MyObject?.edges?.map((edge) => edge?.node) || [];
-}
-```
-
-**Key imports for Pattern 1:**
-
-- `getDataSDK` - Get the DataSDK singleton
-- `NodeOfConnection` - Extract node types from connection responses
-- Query from `.graphql` file with `?raw` suffix
-- Generated types from `graphql-operations-types.ts`
-
-**Pattern 1 Benefits:**
-
-- Full codegen support with automatic type generation
-- Syntax highlighting and validation in `.graphql` files
-- Easier to share queries across multiple files/components
-- Better for complex queries with fragments and multiple variables
-- IDE support for GraphQL (autocomplete, validation)
-- Queries can be tested independently
-- Clear separation of concerns between query definition and usage
-
-**Pattern 1 Limitations:**
-
-- Requires separate file management
-- Extra step to run codegen after query changes
-- More boilerplate (file import with `?raw`, separate file to maintain)
-- Slight overhead for very simple queries
-- Need to navigate between files during development
-- Doesn't support dynamic queries (e.g., the set of fields changes based on runtime conditions and cannot be predetermined)
-
-### Pattern 2: Inline Query with gql Tag (Recommended for simple queries)
-
-For simpler queries without variables or when colocation is preferred:
-
-```typescript
-import { getDataSDK, gql } from "@salesforce/sdk-data";
-import { type CurrentUserQuery } from "../graphql-operations-types";
-
-const CURRENT_USER_QUERY = gql`
-  query CurrentUser {
-    uiapi {
-      currentUser {
-        Id
-        Name {
-          value
-        }
-      }
-    }
-  }
-`;
-
-interface User {
-  id: string;
-  name: string;
-}
-
-export async function getCurrentUser(): Promise<User | null> {
-  try {
-    const data = await getDataSDK();
-    const response = await data.graphql?.<CurrentUserQuery>(CURRENT_USER_QUERY);
-
-    if (response?.errors?.length) {
-      throw new Error(response.errors.map((e) => e.message).join("; "));
-    }
-
-    const userData = response?.data?.uiapi.currentUser;
-
-    if (!userData) {
-      throw new Error("No user data found");
-    }
-
-    return {
-      id: userData.Id,
-      name: userData.Name?.value || "User",
-    };
-  } catch (error) {
-    console.error("Error fetching user data:", error);
-    throw error;
-  }
-}
-```
-
-**Key imports for Pattern 2:**
-
-- `getDataSDK` - Get the DataSDK singleton
-- `gql` - Template tag for inline query definition
-- Generated types from `graphql-operations-types.ts`
-
-**Pattern 2 Benefits:**
-
-- Query is colocated with usage code
-- Supports dynamic queries (e.g., the set of fields changes based on runtime conditions and cannot be predetermined)
-- No separate file to maintain
-- Still gets type-checked against generated types
-- Simpler for straightforward queries
-
-**Pattern 2 Limitations:**
-
-- Inline queries without `gql` template tag are not processed by codegen
-- Must manually ensure query name matches generated types
-- Less suitable for complex queries with fragments
-
-## Conditional Field Selection with Directives
-
-For dynamic fieldsets with known fields that should be conditionally included, use GraphQL directives instead of building queries dynamically. This preserves type generation while allowing runtime control.
-
-### Directives
-
-- **`@include(if: $condition)`** - include field/fragment when `$condition` is `true`
-- **`@skip(if: $condition)`** - skip field/fragment when `$condition` is `true`
-
-### Example with Fragments
-
-```graphql
-query GetAccountDetails($id: ID!, $includeFinancials: Boolean!, $includeContacts: Boolean!) {
-  uiapi {
-    query {
-      Account(where: { Id: { eq: $id } }) {
-        edges {
-          node {
-            Id
-            Name {
-              value
-            }
-            ...FinancialFields @include(if: $includeFinancials)
-            ...ContactFields @include(if: $includeContacts)
-          }
-        }
-      }
-    }
-  }
-}
-
-fragment FinancialFields on Account {
-  AnnualRevenue {
-    value
-  }
-  NumberOfEmployees {
-    value
-  }
-}
-
-fragment ContactFields on Account {
-  Phone {
-    value
-  }
-  Website {
-    value
-  }
-}
-```
-
-### Usage
-
-```typescript
-import { getDataSDK } from "@salesforce/sdk-data";
-import QUERY from "./query/getAccountDetails.graphql?raw";
-import type {
-  GetAccountDetailsQuery,
-  GetAccountDetailsQueryVariables,
-} from "../graphql-operations-types";
-
-const data = await getDataSDK();
-const response = await data.graphql?.<GetAccountDetailsQuery, GetAccountDetailsQueryVariables>(
-  QUERY,
-  {
-    id: accountId,
-    includeFinancials: userWantsFinancials,
-    includeContacts: userWantsContacts,
-  },
-);
-```
-
-## Anti-Patterns (Not Recommended)
-
-### Direct API Calls
-
-```typescript
-// NOT RECOMMENDED: Direct axios/fetch calls for GraphQL
-const response = await axios.post("/graphql", { query });
-
-// PREFERRED: Use the DataSDK
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType>(query, variables);
-```
-
-### Missing Type Definitions
-
-```typescript
-// NOT RECOMMENDED: Untyped GraphQL calls
-const data = await getDataSDK();
-await data.graphql?.(query);
-
-// PREFERRED: Provide response type
-const data = await getDataSDK();
-const response = await data.graphql?.<GetMyDataQuery>(query);
-```
-
-### Plain String Queries (Without gql Tag)
-
-```typescript
-// NOT RECOMMENDED: Plain string queries without gql tag
-const query = `query { ... }`;
-const data = await getDataSDK();
-await data.graphql?.(query);
-
-// PREFERRED: Use gql tag for inline queries
-const QUERY = gql`query { ... }`;
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType>(QUERY);
-
-// OR: Use .graphql file for complex queries
-import QUERY from "./query/myQuery.graphql?raw";
-const data = await getDataSDK();
-const response = await data.graphql?.<ResponseType>(QUERY);
-```
-
-## Benefits of the DataSDK GraphQL API
-
-- Uses the DataSDK with proper authentication and CSRF token handling
-- Consistent typing with `GraphQLResponse<T>` interface
-- Optional chaining (`?.`) safely handles surfaces where GraphQL is unavailable
-- Callers get full `GraphQLResponse<T>` for flexible error handling
-
-## Quality Checklist
-
-Before completing GraphQL data access code:
-
-### For Pattern 1 (.graphql files):
-
-1. [ ] Create `.graphql` file for the query/mutation
-2. [ ] Run `npm run graphql:codegen` to generate types
-3. [ ] Import query with `?raw` suffix
-4. [ ] Import generated types from `graphql-operations-types.ts`
-5. [ ] Use `data.graphql?.<ResponseType>()` with proper generic
-6. [ ] Handle `response.errors` and destructure `response.data`
-7. [ ] Use `NodeOfConnection` for cleaner node types when needed
-8. [ ] Handle optional chaining for nested response data
-9. [ ] Follow the pattern in `accounts.ts`
-
-### For Pattern 2 (inline with gql):
-
-1. [ ] Define query using `gql` template tag
-2. [ ] Ensure query name matches generated types in `graphql-operations-types.ts`
-3. [ ] Import generated types for the query
-4. [ ] Use `data.graphql?.<ResponseType>()` with proper generic
-5. [ ] Handle `response.errors` and destructure `response.data`
-6. [ ] Handle optional chaining for nested response data
-7. [ ] Follow the pattern in `user.ts`
-
-### General:
-
-- [ ] Choose Pattern 1 for complex queries with variables, fragments, or when shared
-- [ ] Choose Pattern 2 for simple, colocated queries without complex requirements

package/dist/.a4drules/skills/feature-graphql-graphql-data-access/SKILL.md

@@ -1,155 +0,0 @@
----
-name: feature-graphql-graphql-data-access
-description: Add or modify Salesforce GraphQL data access code. Use when the user asks to fetch, query, or mutate Salesforce data, or add a GraphQL operation for an object like Account, Contact, or Opportunity.
----
-
-# GraphQL Data Access
-
-Add or modify Salesforce GraphQL data access code using `getDataSDK()` + `data.graphql?.()` and codegen tooling.
-
-## When to Use
-
-- User asks to "fetch data from Salesforce"
-- User asks to "query" or "mutate" Salesforce records
-- User wants to add a new GraphQL operation (query or mutation)
-- User asks to add data access for a Salesforce object (Account, Contact, Opportunity, etc.)
-
-## Prerequisites
-
-The base React app (`base-react-app`) ships with all GraphQL dependencies and tooling pre-configured:
-
-- `@salesforce/sdk-data` — runtime SDK for `getDataSDK` and `gql`
-- `@graphql-codegen/cli` + plugins — type generation from `.graphql` files and inline `gql` queries
-- `@graphql-eslint/eslint-plugin` — linting for `.graphql` files and `gql` template literals
-- `graphql` — shared by codegen, ESLint, and schema introspection
-
-Before using this skill, ensure:
-
-1. The `@salesforce/sdk-data` package is available (provides `getDataSDK`, `gql`, `NodeOfConnection`)
-2. A `schema.graphql` file exists at the project root. If missing, generate it:
-   ```bash
-   npm run graphql:schema
-   ```
-
-## npm Scripts
-
-The base app provides two npm scripts for GraphQL tooling:
-
-- **`npm run graphql:schema`** — Downloads the full GraphQL schema from a connected Salesforce org via introspection. Outputs `schema.graphql` to the project root.
-- **`npm run graphql:codegen`** — Generates TypeScript types from `.graphql` files and inline `gql` queries. Outputs to `src/api/graphql-operations-types.ts`.
-
-## Workflow
-
-### Step 1: Explore the Schema
-
-Before writing any query, verify the target object and its fields exist in the schema.
-
-See `docs/explore-schema.md` for detailed guidance on exploring the Salesforce GraphQL schema.
-
-Key actions:
-
-- Search `schema.graphql` for `type <ObjectName> implements Record` to find available fields
-- Search for `input <ObjectName>_Filter` for filter options
-- Search for `input <ObjectName>_OrderBy` for sorting options
-- For mutations: search for `input <ObjectName>CreateInput` or `<ObjectName>UpdateInput`
-
-### Step 2: Choose the Query Pattern
-
-**Pattern 1 — External `.graphql` file** (recommended for complex queries):
-
-- Queries with variables, fragments, or shared across files
-- Enables full codegen type generation
-- See example: `api/utils/accounts.ts` + `api/utils/query/highRevenueAccountsQuery.graphql`
-
-**Pattern 2 — Inline `gql` tag** (recommended for simple queries):
-
-- Simple queries without variables
-- Colocated with usage code
-- See example: `api/utils/user.ts`
-
-### Step 3: Write the Query
-
-For **Pattern 1**:
-
-1. Create a `.graphql` file under `src/api/utils/query/`
-2. Follow UIAPI structure: `query { uiapi { query { ObjectName(...) { edges { node { ... } } } } } }`
-3. For mutations, see `docs/generate-mutation-query.md`
-4. For read queries, see `docs/generate-read-query.md`
-
-For **Pattern 2**:
-
-1. Define query inline using the `gql` template tag
-2. Ensure the query name matches what codegen expects
-
-### Step 4: Generate Types
-
-```bash
-npm run graphql:codegen
-```
-
-This updates `src/api/graphql-operations-types.ts` with:
-
-- `<OperationName>Query` or `<OperationName>Mutation` — response type
-- `<OperationName>QueryVariables` or `<OperationName>MutationVariables` — input variables type
-
-### Step 5: Implement the Data Access Function
-
-```typescript
-// Pattern 1
-import { getDataSDK, type NodeOfConnection } from "@salesforce/sdk-data";
-import MY_QUERY from "./query/myQuery.graphql?raw";
-import type { GetMyDataQuery, GetMyDataQueryVariables } from "../graphql-operations-types";
-
-type MyNode = NodeOfConnection<GetMyDataQuery["uiapi"]["query"]["MyObject"]>;
-
-export async function getMyData(variables: GetMyDataQueryVariables): Promise<MyNode[]> {
-  const data = await getDataSDK();
-  const response = await data.graphql?.<GetMyDataQuery, GetMyDataQueryVariables>(
-    MY_QUERY,
-    variables,
-  );
-
-  if (response?.errors?.length) {
-    const errorMessages = response.errors.map((e) => e.message).join("; ");
-    throw new Error(`GraphQL Error: ${errorMessages}`);
-  }
-
-  return response?.data?.uiapi?.query?.MyObject?.edges?.map((edge) => edge?.node) || [];
-}
-```
-
-```typescript
-// Pattern 2
-import { getDataSDK, gql } from "@salesforce/sdk-data";
-import type { MySimpleQuery } from "../graphql-operations-types";
-
-const MY_QUERY = gql`
-  query MySimple {
-    uiapi { ... }
-  }
-`;
-
-export async function getSimpleData(): Promise<SomeType> {
-  const data = await getDataSDK();
-  const response = await data.graphql?.<MySimpleQuery>(MY_QUERY);
-  // check response.errors, then extract response.data
-}
-```
-
-### Step 6: Verify
-
-- [ ] Query field names match the schema exactly (case-sensitive)
-- [ ] Response type generic is provided to `data.graphql?.<T>()`
-- [ ] Optional chaining is used for nested response data
-- [ ] Pattern 1: `.graphql` file imported with `?raw` suffix
-- [ ] Pattern 2: Query uses `gql` tag (not plain string)
-- [ ] Generated types imported from `graphql-operations-types.ts`
-
-## Reference
-
-- Schema exploration: `docs/explore-schema.md`
-- Read query generation: `docs/generate-read-query.md`
-- Mutation query generation: `docs/generate-mutation-query.md`
-- Shared GraphQL schema types: `docs/shared-schema.graphqls`
-- Schema download: `npm run graphql:schema` (in the base app)
-- Type generation: `npm run graphql:codegen` (in the base app)