@nimbleams/sfdx-nimbleams
sfdx-nimbleams ========
Last updated a month ago by doggles .
MIT · Repository · Original npm · Tarball · package.json
$ cnpm install @nimbleams/sfdx-nimbleams 
SYNC missed versions from official npm registry.

sfdx-nimbleams

Usage

Install

git clone git@bitbucket.org:nimbleams/sfdx-nimbleams.git
cd sfdx-nimbleams
sfdx plugins:link

Run

sfdx nimbleams:data:import -u USERNAME_OR_ALIAS -f ./data/insertOrder.json

Version Downloads/week

$ npm install -g @nimbleams/sfdx-nimbleams
$ @nimbleams/sfdx-nimbleams COMMAND
running command...
$ @nimbleams/sfdx-nimbleams (-v|--version|version)
@nimbleams/sfdx-nimbleams/1.0.0 darwin-x64 node-v12.2.0
$ @nimbleams/sfdx-nimbleams --help [COMMAND]
USAGE
  $ @nimbleams/sfdx-nimbleams COMMAND
...

@nimbleams/sfdx-nimbleams nimbleams:data:import -f <string> [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

import data using nimbleforce

USAGE
  $ @nimbleams/sfdx-nimbleams nimbleams:data:import -f <string> [-u <string>] [--apiversion <string>] [--json] 
  [--loglevel trace|debug|info|warn|error|fatal]

OPTIONS
  -f, --file=file                                 (required) the path to the manifest file for the data to import
  -u, --targetusername=targetusername             username or alias for the target org; overrides default target org
  --apiversion=apiversion                         override the api version used for api requests made by this command
  --json                                          format output as json
  --loglevel=(trace|debug|info|warn|error|fatal)  [default: warn] logging level for this command invocation

EXAMPLE
  $ sfdx nimbleams:data:import --targetusername myOrg@example.com --file data/insertOrder.json

@nimbleams/sfdx-nimbleams nimbleams:project:add [-k <string>] [-g <string>] [-d <filepath>] [-i <filepath>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

add a new project

USAGE
  $ @nimbleams/sfdx-nimbleams nimbleams:project:add [-k <string>] [-g <string>] [-d <filepath>] [-i <filepath>] [--json] 
  [--loglevel trace|debug|info|warn|error|fatal]

OPTIONS
  -d, --definitionfile=definitionfile                scratch org configuration file
  -g, --gitremote=gitremote                          git remote containing an sfdx project
  -i, --nimbleforceimportfile=nimbleforceimportfile  nimbleforce import file
  -k, --key=key                                      project key
  --json                                             format output as json
  --loglevel=(trace|debug|info|warn|error|fatal)     [default: warn] logging level for this command invocation

EXAMPLE
  $ sfdx nimbleams:project:add

@nimbleams/sfdx-nimbleams nimbleams:project:delete [-f] [--json] [--loglevel trace|debug|info|warn|error|fatal]

delete a project

USAGE
  $ @nimbleams/sfdx-nimbleams nimbleams:project:delete [-f] [--json] [--loglevel trace|debug|info|warn|error|fatal]

ARGUMENTS
  KEY  project key to delete

OPTIONS
  -f, --force                                     skips any prompts and forces delete
  --json                                          format output as json
  --loglevel=(trace|debug|info|warn|error|fatal)  [default: warn] logging level for this command invocation

EXAMPLE
  $ sfdx nimbleams:project:delete AMS

@nimbleams/sfdx-nimbleams nimbleams:project:list [--json] [--loglevel trace|debug|info|warn|error|fatal]

lists all configured projects

USAGE
  $ @nimbleams/sfdx-nimbleams nimbleams:project:list [--json] [--loglevel trace|debug|info|warn|error|fatal]

OPTIONS
  --json                                          format output as json
  --loglevel=(trace|debug|info|warn|error|fatal)  [default: warn] logging level for this command invocation

EXAMPLE
  $ sfdx nimbleams:project:list

@nimbleams/sfdx-nimbleams nimbleams:task:start -p <string> [-t <filepath>] [-b <string>] [-o] [-v <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

start a nimbleams task

USAGE
  $ @nimbleams/sfdx-nimbleams nimbleams:task:start -p <string> [-t <filepath>] [-b <string>] [-o] [-v <string>] 
  [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

ARGUMENTS
  TASK  the task name to start (used for branch name, folder name, and scratch org alias)

OPTIONS
  -b, --branch=branch                              existing branch to start from
  -o, --open                                       open vs code after command is complete
  -p, --project=project                            (required) project key to use for starting task
  -t, --targetdirectory=targetdirectory            target directory to create project folder in
  -v, --targetdevhubusername=targetdevhubusername  username or alias for the dev hub org; overrides default dev hub org
  --apiversion=apiversion                          override the api version used for api requests made by this command
  --json                                           format output as json
  --loglevel=(trace|debug|info|warn|error|fatal)   [default: warn] logging level for this command invocation

EXAMPLES
  $ sfdx nimbleams:task:start AMS-1234 -p AMS
  $ sfdx nimbleams:task:start AMS-1234 -p AMS -t ~/Projects/nu-dx/ -o

Debugging your plugin

We recommend using the Visual Studio Code (VS Code) IDE for your plugin development. Included in the .vscode directory of this plugin is a launch.json config file, which allows you to attach a debugger to the node process when running your commands.

To debug the hello:org command:

  1. Start the inspector

If you linked your plugin to the sfdx cli, call your command with the dev-suspend switch:

$ sfdx hello:org -u myOrg@example.com --dev-suspend

Alternatively, to call your command using the bin/run script, set the NODE_OPTIONS environment variable to --inspect-brk when starting the debugger:

$ NODE_OPTIONS=--inspect-brk bin/run hello:org -u myOrg@example.com
  1. Set some breakpoints in your command code
  2. Click on the Debug icon in the Activity Bar on the side of VS Code to open up the Debug view.
  3. In the upper left hand corner of VS Code, verify that the "Attach to Remote" launch configuration has been chosen.
  4. Hit the green play button to the left of the "Attach to Remote" launch configuration window. The debugger should now be suspended on the first line of the program.
  5. Hit the green play button at the top middle of VS Code (this play button will be to the right of the play button that you clicked in step #5).

    Congrats, you are debugging!

Current Tags

  • 1.0.0                                ...           latest (a month ago)

1 Versions

  • 1.0.0                                ...           a month ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 15
Dependencies (14)
Dev Dependencies (15)
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |