Skip to content
No description, website, or topics provided.
Branch: master
Clone or download
Latest commit 642c46e Jul 19, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src package.json should not be a relative import because paths. Jul 19, 2019
templates Update ts connector (#35) Jul 10, 2019
test Add windows support (#36) Jul 17, 2019
.eslintrc initial commit. Feb 19, 2019
.gitignore Added basic directions for publishing to NPM. Feb 19, 2019
.npmignore Added basic directions for publishing to NPM. Feb 19, 2019
.travis.yml Add windows support (#36) Jul 17, 2019
CONTRIBUTING.md initial commit. Feb 19, 2019
LICENSE initial commit. Feb 19, 2019
README.md docs: Update README with badges, note callouts (#24) May 24, 2019
package.json v2.0.17 Jul 19, 2019
publish-to-npm.sh fix order of publish script. Jul 19, 2019
tsconfig.json Switch to execa (#14) Apr 11, 2019
tslint.json Added a typescript connector template. (#30) Jun 17, 2019
yarn.lock

README.md


dscc-gen

npm Version npm Downloads Package Quality Built with Clasp

Bootstrap a community connector or community viz from the commandline.

Note: dscc-gen requires npm 5.2.0 or later

Running

npx @google/dscc-gen viz or npx @google/dscc-gen connector

Note: dscc-gen supports a few flags. Call with a -h or --help to see options.

dscc-gen will ask a series of questions, then create a new project based on the responses. Once your project has been created, you'll be presented with information with next steps.

What We Collect

To improve dscc-gen over time, we gather the following:

  • Start of Execution
  • Stop of Execution
  • Error Stops of Execution (i.e. an exception was thrown)
  • gsutil was not installed
  • SigInt Stop (i.e. C-c to abort running)

None of this is sent if you opt-out of analytics. To opt out at any time, run rm ~/.config/insight-nodejs/insight-@google/dscc-gen.json and you'll be prompted again the next time you run the tool.

How We Collect

dscc-gen generates a random uuid to identify your computer, and a random uuid to identify an individual run of the tool. An individual run of the tool will look something like: [Execution Starts] -> [Execution Stops].

If you're interested in the weeds of this, check out analytics.ts.

Why We Collect

These analytics are used to:

  • Ensure the tool isn't regularly throwing errors
  • Identify gaps in documentation for common errors
  • Understand how users interact with this tool.
You can’t perform that action at this time.