@salesforce/webapp-template-feature-react-chart-experimental 1.105.1 → 1.106.0

package/dist/AGENT.md

@@ -58,6 +58,10 @@ cd <sfdx-source>/webapplications/<appName>
 
 This project includes **.a4drules/** at the project root. Follow them when generating or editing code.
 
+- **Salesforce Data Access** (`.a4drules/skills/salesforce-data-access/`): Use for all Salesforce data fetches. Enforces Data SDK usage (`createDataSDK()` + `sdk.graphql` or `sdk.fetch`); GraphQL preferred, fetch when GraphQL is not sufficient.
+- **Salesforce REST API Fetch** (`.a4drules/skills/salesforce-rest-api-fetch/`): Use when implementing Chatter, Connect REST, Apex REST, UI API REST, or Einstein LLM calls via `sdk.fetch`.
+- **Salesforce GraphQL** (`.a4drules/skills/salesforce-graphql/`): Use when implementing Salesforce GraphQL queries or mutations. Sub-skills: `salesforce-graphql-explore-schema`, `salesforce-graphql-read-query`, `salesforce-graphql-mutation-query`.
+
 When rules refer to "web app directory" or `<sfdx-source>/webapplications/<appName>/`, resolve `<sfdx-source>` from `sfdx-project.json` and use the **actual app folder name** for this project.
 
 ## Deploying
@@ -79,3 +83,4 @@ sf project deploy start --source-dir <packageDir> --target-org <alias>
 
 - **UI**: shadcn/ui + Tailwind. Import from `@/components/ui/...`.
 - **Entry**: Keep `App.tsx` and routes in `src/`; add features as new routes or sections, don't replace the app shell but you may modify it to match the requested design.
+- **Data (Salesforce)**: Invoke the `salesforce-data-access` skill for all Salesforce data fetches. The skill enforces use of the Data SDK (`createDataSDK()` + `sdk.graphql` or `sdk.fetch`) — never use `fetch` or `axios` directly. GraphQL is preferred; use `sdk.fetch` when GraphQL is not sufficient (e.g., Chatter, Connect REST). For GraphQL implementation, invoke the `salesforce-graphql` skill.

package/dist/CHANGELOG.md

@@ -3,6 +3,17 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [1.106.0](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.105.1...v1.106.0) (2026-03-17)
+
+
+### Features
+
+* **data-skills:** Restructure data knowledge into composable skills ([#296](https://github.com/salesforce-experience-platform-emu/webapps/issues/296)) ([35e0223](https://github.com/salesforce-experience-platform-emu/webapps/commit/35e0223ac8e14c451f204fd206d5ca29fb5e684a))
+
+
+
+
+
 ## [1.105.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.105.0...v1.105.1) (2026-03-17)
 
 **Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental

package/dist/force-app/main/default/webapplications/feature-react-chart/eslint.config.js

@@ -1,3 +1,7 @@
+import { existsSync } from 'node:fs';
+import { resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { dirname } from 'node:path';
 import js from '@eslint/js';
 import tseslint from '@typescript-eslint/eslint-plugin';
 import tsparser from '@typescript-eslint/parser';
@@ -7,7 +11,11 @@ import reactRefresh from 'eslint-plugin-react-refresh';
 import globals from 'globals';
 import graphqlPlugin from '@graphql-eslint/eslint-plugin';
 
-export default [
+const __dirname = dirname(fileURLToPath(import.meta.url));
+const schemaPath = resolve(__dirname, '../../../../../schema.graphql');
+const schemaExists = existsSync(schemaPath);
+
+const config = [
   // Global ignores
   {
     ignores: ['build/**/*', 'dist/**/*', 'coverage/**/*'],
@@ -111,31 +119,38 @@ export default [
       '@typescript-eslint/no-explicit-any': 'off',
     },
   },
-  // GraphQL processor - extracts GraphQL from gql template literals in TS/TSX files
-  {
-    files: ['**/*.{ts,tsx}'],
-    processor: graphqlPlugin.processor,
-  },
-  // GraphQL linting configuration for .graphql files
-  {
-    files: ['**/*.graphql'],
-    languageOptions: {
-      parser: graphqlPlugin.parser,
-      parserOptions: {
-        graphQLConfig: {
-          schema: '../../../../../schema.graphql',
+];
+
+// Only add GraphQL rules when schema exists (e.g. after graphql:schema).
+// In CI or when schema is not checked in, skip so lint succeeds.
+if (schemaExists) {
+  config.push(
+    {
+      files: ['**/*.{ts,tsx}'],
+      processor: graphqlPlugin.processor,
+    },
+    {
+      files: ['**/*.graphql'],
+      languageOptions: {
+        parser: graphqlPlugin.parser,
+        parserOptions: {
+          graphQLConfig: {
+            schema: '../../../../../schema.graphql',
+          },
         },
       },
-    },
-    plugins: {
-      '@graphql-eslint': graphqlPlugin,
-    },
-    rules: {
-      '@graphql-eslint/no-anonymous-operations': 'error',
-      '@graphql-eslint/no-duplicate-fields': 'error',
-      '@graphql-eslint/known-fragment-names': 'error',
-      '@graphql-eslint/no-undefined-variables': 'error',
-      '@graphql-eslint/no-unused-variables': 'error',
-    },
-  },
-];
+      plugins: {
+        '@graphql-eslint': graphqlPlugin,
+      },
+      rules: {
+        '@graphql-eslint/no-anonymous-operations': 'error',
+        '@graphql-eslint/no-duplicate-fields': 'error',
+        '@graphql-eslint/known-fragment-names': 'error',
+        '@graphql-eslint/no-undefined-variables': 'error',
+        '@graphql-eslint/no-unused-variables': 'error',
+      },
+    }
+  );
+}
+
+export default config;

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-base-sfdx-project-experimental",
-  "version": "1.105.1",
+  "version": "1.106.0",
   "description": "Base SFDX project template",
   "license": "SEE LICENSE IN LICENSE.txt",
   "publishConfig": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-feature-react-chart-experimental",
-  "version": "1.105.1",
+  "version": "1.106.0",
   "description": "Chart feature with analytics chart components, agent skills, and rules (Recharts)",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",
@@ -27,7 +27,7 @@
     "clean": "rm -rf dist"
   },
   "devDependencies": {
-    "@salesforce/webapp-experimental": "^1.105.1",
+    "@salesforce/webapp-experimental": "^1.106.0",
     "@types/react": "^19.2.7",
     "@types/react-dom": "^19.2.3",
     "react-dom": "^19.2.1",

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