@mcpher/gas-fakes 1.0.19 → 1.0.21

package/src/support/utils.js

@@ -3,6 +3,7 @@
 import is from '@sindresorhus/is';
 import { assert } from '@sindresorhus/is'
 
+
 const isNU = (item) => is.null(item) || is.undefined(item)
 
 const arrify = (item) => is.array(item)
@@ -128,7 +129,7 @@ export const mergeParamStrings = (...args) => {
       }
       const [_, key, items] = match
       if (!itemMap.has(key)) itemMap.set(key, new Set())
-      const item = itemMap.get(key)      
+      const item = itemMap.get(key)
       assert.set(item)
       items.split(",").forEach(f => itemMap.get(key).add(f))
     })
@@ -376,29 +377,59 @@ const deepEqual = (obj1, obj2) => {
   }
 
   return true;
-};
+}
+
+
+function stringCircular(obj, space = null) {
+  // First pass: remove circular references
+  const withoutCircular = removeCircularReferences(obj);
 
-// The custom replacer function
-const getCircularReplacer = () => {
-  const seen = new WeakSet(); // Use WeakSet to avoid memory leaks
-  return (key, value) => {
-    // If the value is an object and not null
-    if (typeof value === "object" && value !== null) {
-      // If we have already seen this object, it's a circular reference
+  // Second pass: stabilize key order
+  const stabilized = stabilizeKeyOrder(withoutCircular);
+
+  return JSON.stringify(stabilized, null, space);
+}
+
+function removeCircularReferences(obj) {
+  const seen = new WeakSet();
+
+  return JSON.parse(JSON.stringify(obj, (key, value) => {
+    if (typeof value === 'object' && value !== null) {
       if (seen.has(value)) {
-        return "[Circular]"; // Replace it with a placeholder
+        return '[Circular]';
       }
-      // If it's a new object, add it to our cache
       seen.add(value);
     }
-    // Return the value to be serialized
     return value;
-  };
-};
+  }));
+}
+
+function stabilizeKeyOrder(obj) {
+  if (obj === null || typeof obj !== 'object') {
+    return obj;
+  }
+
+  if (Array.isArray(obj)) {
+    return obj.map(stabilizeKeyOrder);
+  }
+
+  const sortedKeys = Object.keys(obj).sort();
+  const result = {};
 
-const stringCircular = (ob) => JSON.stringify(ob, getCircularReplacer());
+  for (const key of sortedKeys) {
+    result[key] = stabilizeKeyOrder(obj[key]);
+  }
 
+  return result;
+}
+const lobify = (ob, mess = '') => {
+  let lob = ob
+  if (is.object(lob)) lob = stringCircular(lob)
+  console.log(mess, lob)
+  return ob
+}
 export const Utils = {
+  lobify,
   stringCircular,
   hexToRgb,
   stringToBytes,

package/src/support/workersync/sxfunctions.js

@@ -1,15 +1,10 @@
-/**
- * This file aggregates and exports all the asynchronous functions
- * that can be called by the main thread via the synchronizer.
- * The worker thread imports this single file to get access to all
- * sx* functions.
- */
-export * from '../sxauth.js';
 export * from '../sxdrive.js';
 export * from '../sxsheets.js';
 export * from '../sxdocs.js';
-export * from '../sxforms.js';
 export * from '../sxslides.js';
-export * from '../sxzip.js';
+export * from '../sxforms.js';
 export * from '../sxfetch.js';
-export * from '../sxstore.js';
+export * from '../sxstore.js';
+export * from '../sxzip.js';
+export * from '../sxauth.js';
+export * from '../sxgmail.js';

package/togas.bash

@@ -25,15 +25,26 @@ cp ${SOURCE}/test*.js ${TARGET}/test
 
 # find all the copied files and comment/fixes out import and export statements
 # note - this simple version naively expects that to be on 1 line
-find "${TARGET}" -name "${EXT}" -type f -exec perl -i -pe 'if (/^import\b/) { $in_import=1 } if ($in_import) { s/^/\/\//; if (/['\''"][^'\''"]*['\''"];?\s*$/) { $in_import=0 } }' {} +
+# version below only works on linux - the perl version should work on both mac and linux
+#find "${TARGET}" -name "${EXT}" -type f -exec perl -i -pe 'if (/^import\b/) { $in_import=1 } if ($in_import) { s/^/\/\//; if (/['\''"][^'\''"]*['\''"];?\s*$/) { $in_import=0 } }' {} +
 # sed -i 's/^import\s\s*/\/\/import /g' $(find "${TARGET}" -name "${EXT}" -type f) 
-sed -i 's/^\s*export\s\s*//g' $(find "${TARGET}" -name "${EXT}" -type f)
+#sed -i 's/^\s*export\s\s*//g' $(find "${TARGET}" -name "${EXT}" -type f)
+
 
+# Perl works consistently across platforms
+find "${TARGET}" -name "${EXT}" -type f -exec perl -i -pe 's/^\s*export\s\s*//g' {} \;
+find "${TARGET}" -name "${EXT}" -type f -exec perl -i -pe 'if (/^import\b/) { $in_import=1 } if ($in_import) { s/^/\/\//; if (/['\''"][^'\''"]*['\''"];?\s*$/) { $in_import=0 } }' {} +
+# sed -i 's/^import\s\s*/\/\/import /g' $(find "${TARGET}" -name "${EXT}" -type f) 
 # replace all process.env.VAR_NAME occurrences with actual value
 # process.env is not usable in apps script
-for var in $(grep -oP 'process\.env\.\K\w+' "${TARGET}/test/testinit.js"); do
-    value=$(printenv "$var")  # Get the environment variable value
+#for var in $(grep -oP 'process\.env\.\K\w+' "${TARGET}/test/testinit.js"); do
+
+# Use macos + linux version
+vars=($(grep -oE 'process\.env\.\w+' "${TARGET}/test/testinit.js" | sed 's/process\.env\.//'))
 
+for var in "${vars[@]}"; do
+
+    value=$(printenv "$var")  # Get the environment variable value
 
     # Escape characters for sed, e.g. \n becomes \\n, & becomes \&
     value=$(printf '%q' "$value")
@@ -44,7 +55,9 @@ for var in $(grep -oP 'process\.env\.\K\w+' "${TARGET}/test/testinit.js"); do
     fi
 
     # Replace process.env.VARIABLE_NAME with the actual value
-    sed -i "s|process.env.$var|$value|g" ${TARGET}/test/testinit.js
+    #sed -i "s|process.env.$var|$value|g" ${TARGET}/test/testinit.js
+    #macos + linux
+    sed -i "" "s|process.env.$var|$value|g" "${TARGET}/test/testinit.js"
 done
 
 # now go to the target and push and open if required

package/ghissues/image-size-inconsistency-issue.sh

@@ -1,46 +0,0 @@
-#!/bin/bash
-
-# A shell script to create a GitHub issue for the image sizing inconsistency.
-
-# Issue title
-TITLE="Investigate and Align Image Insertion Sizing Behavior"
-
-# Issue body in markdown
-BODY=$(cat <<'EOF'
-## Summary
-
-There is a significant and inconsistent discrepancy in how the live `DocumentApp` service and the `gas-fakes` emulation (via the Docs API) handle the dimensions of an image when it is inserted using `body.insertImage(image.copy())` or `body.appendImage(image.copy())`.
-
-The `testdocsimages.js` test suite has repeatedly failed and required adjustments because the expected dimensions of the inserted image are unpredictable in the live environment.
-
-## Observed Behaviors in Live Apps Script
-
-Our testing has revealed several conflicting behaviors from the live API:
-
-1.  **Intrinsic Size:** Sometimes, the API ignores the dimensions of the copied `InlineImage` object and re-fetches the image from its source URI, using its original intrinsic dimensions (e.g., `544x184` for the Google logo).
-2.  **Copied Object Size:** At other times, the API correctly respects the dimensions of the copied `InlineImage` object (e.g., `61x181` in our tests).
-3.  **Default/Fixed Size:** On at least one occasion, the API appeared to resize the image to a seemingly arbitrary fixed size (e.g., `240x80`).
-4.  **State-Dependent:** The behavior seems to be dependent on the state of the document. A brand-new document might exhibit one behavior, while a reused document (even after `doc.clear()`) exhibits another.
-
-## Current Workaround
-
-The current test (`insertImage behavior on new documents` in `testdocsimages.js`) has been made more robust by:
-- Forcing the creation of a new document for the test using `maketdoc(..., { forceNew: true })`.
-- Abandoning exact dimension checks in the live environment and instead verifying the image's **aspect ratio** within a tolerance.
-
-While this makes the test pass, it highlights a core emulation inaccuracy.
-
-## TODO
-
-1.  **Investigate Further:** Conduct a definitive set of tests to determine if there is *any* predictable pattern to the live API's behavior.
-2.  **Decide on Emulation Strategy:**
-    - Should `gas-fakes` emulate the most common or most "correct" behavior (i.e., respecting the copied object's dimensions)?
-    - Or should it attempt to mimic the most recently observed "new document" behavior (using intrinsic size)?
-3.  **Document the Oddity:** Regardless of the chosen strategy, this inconsistency is a significant "oddity" and should be thoroughly documented in `oddities.md` to inform users who might encounter similar issues when working with images in `DocumentApp`.
-
-This will improve the accuracy of the fake environment and provide valuable documentation for the community.
-EOF
-)
-
-# Create the issue using GitHub CLI
-gh issue create --title "$TITLE" --body "$BODY" --label "bug" --label "emulation-accuracy" --label "document-app"

package/ghissues/issue-formapp-create-title-inconsistency.sh

@@ -1,51 +0,0 @@
-#!/bin/bash
-
-# A shell script to create a GitHub issue for the FormApp.create() title inconsistency.
-
-# Issue title
-TITLE="Discrepancy between FormApp.create(title) and Forms API behavior regarding form title and file name"
-
-# Issue body in markdown
-BODY=$(cat <<'EOF'
-### Summary
-
-There is a significant and counter-intuitive discrepancy between the documented behavior of `FormApp.create(title)` in Google Apps Script and the constraints of the underlying Google Forms API. `FormApp.create(title)` sets the Google Drive *file name* to the provided `title`, but leaves the form's internal title (retrieved by `form.getTitle()`) blank.
-
-This makes it impossible to accurately emulate the Apps Script behavior using the public Forms API, as the API requires a non-empty title for both creation and updates.
-
-### Live Apps Script Behavior
-
-When the following Apps Script code is executed:
-
-```javascript
-function testFormCreation() {
-  const formName = "foo-form";
-  const form = FormApp.create(formName);
-  const id = form.getId();
-  
-  console.log('Internal form title:', form.getTitle()); // Logs: "" (an empty string)
-  
-  const file = DriveApp.getFileById(id);
-  console.log('Drive file name:', file.getName());   // Logs: "foo-form"
-  
-  // cleanup
-  file.setTrashed(true);
-}
-```
-
-The output demonstrates that `FormApp.create()` uses the argument to set the Drive file name, but the form's own title property remains empty.
-
-### The Problem with API Emulation
-
-This behavior is problematic to replicate with the v1 Google Forms API because the `forms.create` method requires a non-empty `info.title`. Attempting to then `batchUpdate` the title to an empty string also fails, as the API rejects an empty title on update.
-
-### Conclusion
-
-This disconnect means it's impossible for developers using the public Forms API to programmatically create a form that exactly matches the state of one created by `FormApp.create()`. This poses a significant challenge for testing and emulation frameworks.
-
-The expected behavior would be for `FormApp.create(title)` to set both the Drive file name and the internal form title, or for the API to allow setting the title to an empty string via an update.
-EOF
-)
-
-# Create the issue using GitHub CLI
-gh issue create --title "$TITLE" --body "$BODY" --label "bug" --label "emulation-accuracy" --label "form-app"

package/ghissues/issue-positioned-image.sh

@@ -1,25 +0,0 @@
-#!/bin/bash
-
-# A script to create a GitHub issue for the PositionedImage API limitation.
-
-# Issue details
-TITLE="Cannot emulate Paragraph.addPositionedImage() due to missing public API"
-BODY=$(cat <<'EOF'
-The `DocumentApp.Paragraph.addPositionedImage()` method exists in the live Google Apps Script environment, allowing for the creation of positioned images anchored to a paragraph.
-
-However, as of May 2024, there is no corresponding public endpoint in the Google Docs API v1 to programmatically create a `PositionedObject`. The `createPositionedObject` request does not exist in the public API.
-
-This has been a requested feature, but it appears that the Apps Script service uses a private, non-public API to achieve this functionality.
-
-Because `gas-fakes` relies exclusively on the public Google Workspace APIs, it is not possible to emulate this method. Tests that use `addPositionedImage` are skipped when run in the fake environment.
-
-This issue is to track this limitation and can be closed if Google exposes a public API for this feature.
-
-See this related issue tracker for the API feature request: https://issuetracker.google.com/issues/183845501 (Note: This is a guess at a relevant issue, a real one might need to be found or created).
-EOF
-)
-LABELS="emulation-accuracy,document-app"
-
-# Create the issue using the GitHub CLI
-gh issue create --title "$TITLE" --body "$BODY" --label "$LABELS"
-

package/ghissues/post-issue.sh

@@ -1,53 +0,0 @@
-#!/bin/bash
-
-# A shell script to post a markdown file from ./ghissues as a GitHub issue.
-# It automatically extracts the title, labels, and body from the file.
-#
-# Usage: ./ghissues/post-issue.sh <filename>
-# Example: ./ghissues/post-issue.sh document-clear-behavior.md
-
-set -e
-
-# The directory where issue files are stored, relative to the script's location.
-SCRIPT_DIR=$(dirname "$0")
-
-# Check for filename argument
-if [ -z "$1" ]; then
-  echo "Usage: $0 <filename_in_ghissues_dir>"
-  echo "Example: $0 document-clear-behavior.md"
-  exit 1
-fi
-
-ISSUE_FILE="$SCRIPT_DIR/$1"
-
-# Check if file exists
-if [ ! -f "$ISSUE_FILE" ]; then
-    echo "Error: Issue file not found at $ISSUE_FILE"
-    exit 1
-fi
-
-echo "Reading issue from $ISSUE_FILE..."
-
-# Extract the title (first line, remove markdown heading)
-TITLE=$(head -n 1 "$ISSUE_FILE" | sed 's/^# //')
-
-# Extract labels from the second line (e.g., **Labels**: `label1`, `label2`)
-LABELS_LINE=$(sed -n '2p' "$ISSUE_FILE")
-LABELS_STRING=$(echo "$LABELS_LINE" | grep -o '`.*`' | sed 's/`//g' || echo "")
-
-LABEL_ARGS=()
-if [ -n "$LABELS_STRING" ]; then
-  IFS=',' read -ra ADDR <<< "$LABELS_STRING"
-  for label in "${ADDR[@]}"; do
-      trimmed_label=$(echo "$label" | xargs) # trim whitespace
-      if [ -n "$trimmed_label" ]; then
-          LABEL_ARGS+=("--label" "$trimmed_label")
-      fi
-  done
-fi
-
-# Use the rest of the file (from line 3) as the body
-gh issue create --title "$TITLE" --body-file <(tail -n +3 "$ISSUE_FILE") "${LABEL_ARGS[@]}"
-
-echo "Issue '$TITLE' created successfully."
-

package/ghissues/protection-editors-issue.sh

@@ -1,33 +0,0 @@
-#!/bin/bash
-
-# A shell script to create a GitHub issue for the Protection.getEditors() behavior.
-
-# Issue title
-TITLE="Align Protection.getEditors() behavior with Live Apps Script"
-
-# Issue body in markdown
-BODY=$(cat <<'EOF'
-## Summary
-
-There is a discrepancy between the live Google Apps Script environment and the `gas-fakes` emulation regarding the return value of `Protection.getEditors()` on a newly created protection.
-
--   **Live Apps Script:** `protection.getEditors().length` returns `0`.
--   **`gas-fakes` (current):** `protection.getEditors().length` incorrectly returns `1`.
-
-## Live Behavior Details
-
-In the live environment, the owner of a spreadsheet can always edit a protected range or sheet (`protection.canEdit()` returns `true`). However, the owner is **not** automatically included in the explicit list of editors returned by `getEditors()`. This is confirmed by live testing.
-
-## `gas-fakes` Behavior
-
-The `gas-fakes` implementation in `fakeprotection.js` was incorrectly adding the current user (as the owner) to the list of editors upon creation of a new `Protection` object.
-
-## TODO
-
-1.  Modify `fakeprotection.js` to no longer automatically add the owner to the `editors` list when a new protection is created. The `canEdit()` method should still return `true` for the owner.
-2.  Run the full test suite to ensure this change doesn't have unintended side effects and that the `Protection` tests now pass in both environments.
-EOF
-)
-
-# Create the issue using GitHub CLI
-gh issue create --title "$TITLE" --body "$BODY" --label "bug" --label "emulation-accuracy" --label "spreadsheet-app"

package/ghissues/review-sandbox-listing-issue.sh

@@ -1,45 +0,0 @@
-#!/bin/bash
-
-# A shell script to create a GitHub issue for reviewing sandbox listing behavior.
-
-# Issue title
-TITLE="Review Sandbox Strategy for File Listing Operations"
-
-# Issue body in markdown
-BODY=$(cat <<'EOF'
-## Summary
-
-Currently, tests that perform broad file/folder listing operations (e.g., `DriveApp.getFiles()`, `someFolder.getFolders()`) fail when `strictSandbox` is `true`. This is because the underlying iterators may need to access metadata of parent folders that are not explicitly whitelisted, causing the sandbox to correctly deny access.
-
-The current workaround, as implemented in `testdrive.js`, is to temporarily disable `strictSandbox` for the duration of these tests:
-
-```javascript
-const wasStrict = behavior.strictSandbox;
-behavior.strictSandbox = false;
-try {
-  // ... listing operations ...
-} finally {
-  behavior.strictSandbox = wasStrict;
-}
-```
-
-While this works, it feels like a patch rather than a fundamental solution. We should review if there's a more robust and elegant way to handle this.
-
-## TODO
-
-Investigate and decide on the best long-term strategy for handling file listings in strict sandbox mode.
-
-### Options to Consider:
-
-1.  **Implicit Parent Whitelisting:** Could the file/folder iterators be enhanced to automatically (and temporarily) whitelist parent folders as they are encountered? This would keep the sandbox strict for all other operations but allow listings to complete. This seems like the most robust solution if feasible.
-
-2.  **Refined Iterator Logic:** Can the iterators be modified to avoid the specific checks that cause the failure when in strict mode? This might involve fetching less metadata for items outside the session/whitelist scope.
-
-3.  **Accept and Document:** If the current `try...finally` workaround is deemed the most practical approach, we should formally document it in `sandbox.md` as the recommended pattern for this scenario.
-
-This review will help ensure the sandbox feature is both as secure and as user-friendly as possible.
-EOF
-)
-
-# Create the issue using GitHub CLI
-gh issue create --title "$TITLE" --body "$BODY" --label "enhancement"

package/ghissues/sandbox-issue.sh

@@ -1,31 +0,0 @@
-#!/bin/bash
-
-# A shell script to create a GitHub issue for the sandbox feature.
-
-# Issue title
-TITLE="Improve Sandbox Mode to fully emulate drive.file scope"
-
-# Issue body in markdown
-BODY=$(cat <<'EOF'
-## Summary
-
-The current implementation of `gas-fakes` requires the full `https://www.googleapis.com/auth/drive` scope for initialization, primarily to access metadata about the root Drive folder. This is a stumbling block for users who want to run tests in a more restrictive environment using only the `drive.file` scope.
-
-The `ScriptApp.__behavior.sandBoxMode` was introduced as a clever workaround to *emulate* the `drive.file` scope during test execution, but it doesn't solve the initial authorization requirement.
-
-For more details on the current sandbox implementation, see sandbox.md.
-
-## TODO
-
-We need to investigate ways to remove the dependency on root folder access during the `FakeDriveApp` initialization. This would allow `gas-fakes` to operate with only the `drive.file` scope, making the sandbox feature a true end-to-end emulation.
-
-Possible areas to explore:
-- Can we mock or bypass the root folder check during initialization if a specific `drive.file` mode is detected?
-- Can we lazy-initialize parts of `FakeDriveApp` that require root access, and only fail if those specific methods (like `getRootFolder()`) are called without sufficient permissions?
-
-This would be a significant improvement for security-conscious development and testing workflows.
-EOF
-)
-
-# Create the issue using GitHub CLI
-gh issue create --title "$TITLE" --body "$BODY" --label "enhancement" --label "help wanted"

package/ghissues/setup-under-construction.sh

@@ -1,107 +0,0 @@
-#!/bin/bash
-
-echo "Welcome to the gas-fakes configuration tool!"
-echo "This script will help you set up your .env and gasfakes.json files."
-
-# --- Check for existing .env file ---
-if [ -f ".env" ]; then
-    echo ""
-    echo "An existing .env file was found. We will update the values."
-    UPDATE_MODE=true
-else
-    echo ""
-    echo "No .env file found. We will create a new one."
-    UPDATE_MODE=false
-fi
-
-# --- Get .env file details ---
-echo ""
-echo "First, let's configure your .env file for Application Default Credentials (ADC)."
-echo "These are necessary for gas-fakes to access Google Workspace APIs on your behalf."
-
-read -p "Enter your Google Cloud Project ID: " gcp_project_id
-read -p "Enter the ID of a Google Drive file you have access to: " drive_test_file_id
-read -p "Enter the default scopes (e.g., \"https://www.googleapis.com/auth/userinfo.email,openid,https://www.googleapis.com/auth/cloud-platform\"): " default_scopes
-read -p "Enter any EXTRA_SCOPES (e.g., ,https://www.googleapis.com/auth/drive,https://www.googleapis.com/auth/spreadsheets): " extra_scopes
-
-# --- Update or create .env file ---
-if [ "$UPDATE_MODE" = true ]; then
-    # Use sed to replace the values in the existing file
-    sed -i "s|^GCP_PROJECT_ID=.*|GCP_PROJECT_ID=$gcp_project_id|" .env
-    sed -i "s|^DRIVE_TEST_FILE_ID=.*|DRIVE_TEST_FILE_ID=$drive_test_file_id|" .env
-    sed -i "s|^DEFAULT_SCOPES=.*|DEFAULT_SCOPES=\"$default_scopes\"|" .env
-    sed -i "s|^EXTRA_SCOPES=.*|EXTRA_SCOPES=\"$extra_scopes\"|" .env
-    echo ""
-    echo "Successfully updated the .env file."
-else
-    # Write a new .env file
-    cat <<EOF > .env
-# Required for gas-fakes to use Application Default Credentials
-GCP_PROJECT_ID="$gcp_project_id"
-DRIVE_TEST_FILE_ID="$drive_test_file_id"
-
-# This should generally be left as default for ADC
-AC=default
-
-# These are the scopes set by default - customize as needed
-DEFAULT_SCOPES="$default_scopes"
-
-# Add additional scopes here
-EXTRA_SCOPES="$extra_scopes"
-EOF
-    echo ""
-    echo "Successfully created the .env file."
-fi
-
-# --- Get gasfakes.json details ---
-echo ""
-echo "Next, let's configure your gasfakes.json file."
-echo "This file informs gas-fakes about your local environment."
-
-# Using default values as suggested by the repository
-DEFAULT_MANIFEST="./appsscript.json"
-DEFAULT_CLASP="./.clasp.json"
-DEFAULT_CACHE="/tmp/gas-fakes/cache"
-DEFAULT_PROPERTIES="/tmp/gas-fakes/properties"
-DEFAULT_SCRIPT_ID=$(uuidgen) # A fake script ID if clasp file is not used
-
-read -p "Enter the path to your manifest file (default: $DEFAULT_MANIFEST): " manifest_path
-manifest_path=${manifest_path:-$DEFAULT_MANIFEST}
-
-read -p "Enter the path to your clasp file (default: $DEFAULT_CLASP): " clasp_path
-clasp_path=${clasp_path:-$DEFAULT_CLASP}
-
-read -p "Enter a bound document ID if applicable (leave blank for none): " document_id
-if [ -z "$document_id" ]; then
-    document_id="null"
-else
-    document_id="\"$document_id\""
-fi
-
-read -p "Enter the local cache directory (default: $DEFAULT_CACHE): " cache_path
-cache_path=${cache_path:-$DEFAULT_CACHE}
-
-read -p "Enter the local properties directory (default: $DEFAULT_PROPERTIES): " properties_path
-properties_path=${properties_path:-$DEFAULT_PROPERTIES}
-
-read -p "Enter the script ID (default: a new random ID will be created): " script_id
-script_id=${script_id:-$DEFAULT_SCRIPT_ID}
-
-# --- Write gasfakes.json file ---
-cat <<EOF > gasfakes.json
-{
-    "manifest": "$manifest_path",
-    "clasp": "$clasp_path",
-    "documentId": $document_id,
-    "cache": "$cache_path",
-    "properties": "$properties_path",
-    "scriptId": "$script_id"
-}
-EOF
-
-echo ""
-echo "Successfully created the gasfakes.json file."
-
-echo ""
-echo "Setup complete! You can now run your gas-fakes project locally."
-echo "Be sure to follow the remaining setup instructions in the gas-fakes repository."

package/src/services/base/app.js

@@ -1,33 +0,0 @@
-
-/**
- * fake Apps Script Session
- * the idea here is to create a global entry for the singleton 
- * before we actually have everything we need to create it. 
- * We do this by using a proxy, intercepting calls to the 
- * initial sigleton and diverting them to a completed one
- */
-
-import { Proxies } from '../../support/proxies.js'
-import { newFakeSession } from './fakesession.js'
-
-let _app = null
-
-/**
- * adds to global space to mimic Apps Script behavior
- */
-const name = "Session"
-if (typeof globalThis[name] === typeof undefined) {
-
-  const getApp = () => {
-    // if it hasn't been intialized yet then do that
-    if (!_app) {
-      console.log('...activating proxy for', name)
-      _app = newFakeSession()
-    }
-    // this is the actual driveApp we'll return from the proxy
-    return _app
-  }
-
-  Proxies.registerProxy(name, getApp)
-
-}