@salesforce/webapp-template-feature-react-authentication-experimental 1.101.1 → 1.101.3

package/dist/.a4drules/skills/feature-graphql-graphql-data-access/docs/generate-mutation-query.md

@@ -173,15 +173,21 @@ const QUERY_VARIABLES = {
 
 **Workflow**
 
-1. **Report Step** - Explain that you are able to test the query using the same method used during introspection
-   1. You **MUST** report the method you will use, based on the one you used during schema exploration
-2. **Interactive Step** - Ask the user whether they want you to test the query using the proposed method
+1. **Report Step** - Explain that you are able to test the query using `sf api request rest`
+2. **Interactive Step** - Ask the user whether they want you to test the query
    1. **WAIT** for the user's answer.
 3. **Input Arguments** - You **MUST** ask the user for the input arguments to use
    1. **WAIT** for the user's answer.
 4. **Test Query** - If the user are OK with you testing the query:
-   1. Use the selected method to test the query
-   2. **IMPORTANT** - If you use the Salesforce CLI `sf api request graphql` command, you will need to inject the variable values directly into the query, as this command doesn't accept variables as a parameter
+   1. Use `sf api request rest` to POST the query and variables to the GraphQL endpoint:
+      ```bash
+      sf api request rest /services/data/v65.0/graphql \
+        --method POST \
+        --body '{"query":"mutation mutateEntity($input: EntityNameOperationInput!) { uiapi { EntityNameOperation(input: $input) { Record { Id } } } }","variables":{"input":{"EntityName":{"Field":"Value"}}}}'
+      ```
+   2. Replace `v65.0` with the API version of the target org
+   3. Replace the `query` value with the generated mutation query string
+   4. Replace the `variables` value with the user-provided input arguments
 5. **Result Analysis** - Retrieve the `data` and `errors` attributes from the returned payload, and report the result of the test as one of the following options:
    1. `PARTIAL` if `data` is not an empty object, but `errors` is not an empty list - Explanation: some of the queried fields are not accessible on mutations
    2. `FAILED` if `data` is an empty object - Explanation: the query is not valid

package/dist/.a4drules/skills/feature-graphql-graphql-data-access/docs/generate-read-query.md

@@ -168,14 +168,21 @@ const QUERY_VARIABLES = {
 
 **Workflow**
 
-1. **Report Step** - Explain that you are able to test the query using the same method used during introspection
-   1. You **MUST** report the method you will use, based on the one you used during schema exploration
-2. **Interactive Step** - Ask the user whether they want you to test the query using the proposed method
+1. **Report Step** - Explain that you are able to test the query using `sf api request rest`
+2. **Interactive Step** - Ask the user whether they want you to test the query
    1. **WAIT** for the user's answer.
 3. **Test Query** - If the user are OK with you testing the query:
-   1. Use the selected method to test the query
-   2. Report the result of the test as `SUCCESS` if the query executed without error, or `FAILED` if you got errors
-   3. If the query executed without any errors, but you received no data, then the query is valid, and the result of the test is `SUCCESS`
+   1. Use `sf api request rest` to POST the query to the GraphQL endpoint:
+      ```bash
+      sf api request rest /services/data/v65.0/graphql \
+        --method POST \
+        --body '{"query":"query GetData { uiapi { query { EntityName { edges { node { Id } } } } } }"}'
+      ```
+   2. Replace `v65.0` with the API version of the target org
+   3. Replace the `query` value with the generated read query string
+   4. If the query uses variables, include them in the JSON body as a `variables` key
+   5. Report the result of the test as `SUCCESS` if the query executed without error, or `FAILED` if you got errors
+   6. If the query executed without any errors, but you received no data, then the query is valid, and the result of the test is `SUCCESS`
 4. **Remediation Step** - If status is `FAILED`, use the [`FAILED` status handling workflows](#failed-status-handling-workflow)
 
 ### `FAILED` Status Handling Workflow

package/dist/CHANGELOG.md

@@ -3,6 +3,22 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [1.101.3](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.101.2...v1.101.3) (2026-03-14)
+
+**Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental
+
+
+
+
+
+## [1.101.2](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.101.1...v1.101.2) (2026-03-14)
+
+**Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental
+
+
+
+
+
 ## [1.101.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v1.101.0...v1.101.1) (2026-03-13)
 
 **Note:** Version bump only for package @salesforce/webapp-template-base-sfdx-project-experimental

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-base-sfdx-project-experimental",
-  "version": "1.101.1",
+  "version": "1.101.3",
   "description": "Base SFDX project template",
   "private": true,
   "files": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/webapp-template-feature-react-authentication-experimental",
-  "version": "1.101.1",
+  "version": "1.101.3",
   "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.101.1",
+    "@salesforce/webapp-experimental": "^1.101.3",
     "@tanstack/react-form": "^1.27.7",
     "@types/react": "^19.2.7",
     "@types/react-dom": "^19.2.3",