Import/Export sample - minor fixes

- Remove deprecated gulp-clean module from npm dependencies
- New simpler “clean” implementations in gulp file.
- README fit and polish

Author: hess-g

import_export_development/README.md

@@ -7,18 +7,19 @@ This sample uses the community project [node-google-apps-script](https://www.npm
 1. run `npm install -g node-google-apps-script` to install it globally. This will allow you to run a few of the steps below from the command line.
 2. Go through the [configuration and authorization steps](https://www.npmjs.com/package/node-google-apps-script).
 2. Run `npm install -g gulp` if you do not already have the [gulp](http://gulpjs.com/) task runner installed globally.
-3. Clone this repository, `cd google-apps-script-samples\import_export_development`, and run `npm install`. This will set up all of the local dependencies for the project.
+3. Clone this repository, `cd google-apps-script-samples/import_export_development`, and run `npm install`. This will set up all of the local dependencies for the project.
 
 ### Demonstrating the developer flow
 To get the initial setup working for you, perform the following steps. In a real project, each developer would perform these steps, so that they can do development in isolation from other developers:
 
 1. Create a [new Google Spreadsheet](https://docs.google.com/spreadsheets/create), and copy the ID of the file. The file ID is found in the URL to the spreadsheet:
 	docs.google.com/spreadsheets/d/***DRIVE_FILE_ID***/edit#gid=123
-2. Open the file *src\environments\dev\debug.local.config.js*, and replace DRIVE_FILE_ID with the ID that you copied.
+2. Open the file *src/environments/dev/debug.local.config.js*, and replace DRIVE_FILE_ID with the ID that you copied.
 3. Create a new standalone [Google Apps Script](https://script.google.com) project, and copy the ID of the script. The file ID is found in the URL to the script project:
 	script.google.com/a/macros/google.com/d/***DRIVE_FILE_ID***/edit
 4. Perform the following commands:
 ```
+mkdir build
 cd build
 mkdir dev
 cd dev
@@ -35,7 +36,7 @@ You can run the code either by publishing it as a web app, or testing it as an a
 This second phase mimics the setup to isolate testing from development. This would typically be a single Apps Script file for the project, and would have some different code added to enable testing scenarios. In a real project, a testing coordinator or other similar role would perform these steps:
 
 1. Create a [new Google Spreadsheet](https://docs.google.com/spreadsheets/create), and copy the ID of the file. Add 4 additional sheets to the file (the test looks for 5 sheets).
-2. Open the file *src\environments\tst\a.myproj.tst.config.js*, and replace DRIVE_FILE_ID with the ID that you copied.
+2. Open the file *src/environments/tst/a.myproj.tst.config.js*, and replace DRIVE_FILE_ID with the ID that you copied.
 3. Perform the same steps #3 and #4 from above, replacing `dev` with `tst`.
 4. Refresh the Apps Script project, open the file `a.myproj.tests.server.main.js`, and then run the function `runAllTests`. Once the run completes, open the log view to see the output.
 
@@ -47,7 +48,7 @@ This final phase mimics the setup to prepare for a production deployment. This w
 
 
 1. Perform the same steps #3 and #4 from above, replacing `dev` with `prd`.
-2. Refresh the Apps Script project, open the script properties, and click on the "Scopes" tab. You will see that the spreadsheet scope now only allows the current attached doc, which is what we would want for production.
+2. Refresh the Apps Script project, open the project properties (File --> Project properties), and click on the "Scopes" tab. You will see that the spreadsheet scope now only allows the current attached doc (`spreadsheets.currentonly`), which is what we would want for production.
 3. You can also create a new spreadsheet, set up for add-on testing, and the code will run successfully.
 
 For production, the configuration file does *not* have a specific spreadsheet, and has the annotation @onlycurrent doc. That will ensure that only Spreadsheets that the code has been linked via the Add-on can be accessed. This limiting of scope is a good practice to provide more confidence to your users that you are only working on sheets that they have linked to your add-on.

import_export_development/gulpfile.js

@@ -19,8 +19,8 @@ var jshint = require('gulp-jshint');
 var shell = require('gulp-shell');
 var minimist = require('minimist');
 var rename = require('gulp-rename');
-var clean = require('gulp-clean');
 var debug = require('gulp-debug');
+var del = require('del');
 
 // minimist structure and defaults for this task configuration
 var knownOptions = {
@@ -104,15 +104,17 @@ function copyEnvironmentSpecific() {
 
 // Utility tasks
 gulp.task('clean-deployment', function(cb) {
-  return gulp.src(dstRoot + '/*.*', {read: false})
-      .pipe(clean());
+  return del([
+    dstRoot + '/*.*'
+  ]);
 });
 
 gulp.task('clean-deployments', function(cb) {
-  return gulp.src(['build/dev/src/*.*',
-                   'build/tst/src/*.*' ,
-                   'build/prd/src/*.*'], {read: false})
-      .pipe(clean());
+  return del([
+    'build/dev/src/*.*',
+    'build/tst/src/*.*' ,
+    'build/prd/src/*.*'
+  ]);
 });
 
 gulp.task('lint', function() {

import_export_development/package.json

@@ -1,15 +1,16 @@
 {
   "author": "[email protected]",
   "dependencies": {
+    "del": "^2.2.0",
     "gulp": "^3.9.0",
-    "gulp-clean": "^0.3.1",
     "gulp-debug": "^2.1.2",
     "gulp-jshint": "^1.12.0",
     "gulp-rename": "^1.2.2",
     "gulp-shell": "^0.5.1",
     "jshint-stylish": "^2.0.1",
     "minimist": "^1.2.0",
-    "node-google-apps-script": "^1.1.3"
+    "node-google-apps-script": "^1.1.3",
+    "vinyl-paths": "^2.1.0"
   },
   "description": "A sample showing command line tool techniques that can be used when developing for Google Apps Script projects.",
   "keywords": [
@@ -23,7 +24,6 @@
     "type": "git",
     "url": "https://github.com/tbd"
   },
-  "scripts": {
-  },
+  "scripts": {},
   "version": "1.0.0"
 }