We have a solution based on Cloud Functions and Google Sheet (AppsScript). Under the solution root folder, there is a folder named 'apps_script' which contains js files and appscript.json that will be pushed to the newly created Google Sheet(Script) during the installation. There are other folders for other parts, e.g. Cloud Functions, etc.
We use clasp to help user create a new Google Sheet and push the codes into it.
Expected Behavior
We use following cmd to create a new project:
clasp create --type sheets --title 'test' --rootDir ./apps_script
The .clasp.json should be generated under the solution root folder, so the following clasp push can pick up the config and do the work.
Actual Behavior
The .clasp.json was generated under the folder apps_script, then the next cmd clasp push failed due to there is no valid .clasp.json project file.
There is no way to guide clasp push to know where is the .clasp.json.
I am pretty sure that it was the case before. It also says in the README:
When running clone or create, a file named .clasp.json is created in the current directory to describe clasp's configuration for the current project.
We have a solution based on Cloud Functions and Google Sheet (AppsScript). Under the solution root folder, there is a folder named 'apps_script' which contains js files and
appscript.json
that will be pushed to the newly created Google Sheet(Script) during the installation. There are other folders for other parts, e.g. Cloud Functions, etc.We use
clasp
to help user create a new Google Sheet and push the codes into it.Expected Behavior
We use following cmd to create a new project:
clasp create --type sheets --title 'test' --rootDir ./apps_script
The.clasp.json
should be generated under the solution root folder, so the followingclasp push
can pick up the config and do the work.Actual Behavior
The
.clasp.json
was generated under the folderapps_script
, then the next cmdclasp push
failed due to there is no valid.clasp.json
project file. There is no way to guideclasp push
to know where is the.clasp.json
. I am pretty sure that it was the case before. It also says in the README:Steps to Reproduce the Problem
Specifications
node -v
): v16.14.2clasp -v
): 2.4.1