You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My old scripts that worked for version v0.4.7 no longer work with v0.4.9 which was released last month.
As far as I can tell the parameter names are the same.
This causing the help information to be displayed:
Usage: gen-schema-views [options]
Generate strongly-typed BigQuery Views based on raw JSON
Options:
-V, --version output the version number
--non-interactive Parse all input from command line flags instead of prompting the caller. (default: false)
-P, --project Firebase Project ID for project containing Cloud Firestore database.
-B, --big-query-project Google Cloud Project ID for BigQuery (can be the same as the Firebase project ID).
-d, --dataset The ID of the BigQuery dataset containing a raw Cloud Firestore document changelog.
-t, --table-name-prefix A common prefix for the names of all views generated by this script.
-f, --schema-files A collection of files from which to read schemas. (default: [])
-h, --help display help for command
Expected result
View is created.
Actual result
Help info displayed as above.
Fix:
Run:
npm install @firebaseextensions/[email protected]
Run the command above again and it works.
The text was updated successfully, but these errors were encountered:
[REQUIRED] Step 3: Describe the problem
My old scripts that worked for version v0.4.7 no longer work with v0.4.9 which was released last month.
As far as I can tell the parameter names are the same.
Steps to reproduce:
Run:
npx @firebaseextensions/fs-bq-schema-views --non-interactive --project="projectname" --dataset="datasetname" --table-name-prefix="tags" --schema-files="./Schemas/tags.json"
Expected result
View is created.
Actual result
Help info displayed as above.
Fix:
Run:
npm install @firebaseextensions/[email protected]
Run the command above again and it works.
The text was updated successfully, but these errors were encountered: