@vprok/debug-reset-webinar
==========================

Apex logs reset plugin demo

![Version](https://npmjs.org/package/@vprok/debug-reset-webinar)
![CircleCI](https://circleci.com/gh/appsolutelysf/debug-reset-webinar/tree/master)
![Appveyor CI](https://ci.appveyor.com/project/heroku/debug-reset-webinar/branch/master)
![Codecov](https://codecov.io/gh/appsolutelysf/debug-reset-webinar)
![Greenkeeper](https://greenkeeper.io/)
![Known Vulnerabilities](https://snyk.io/test/github/appsolutelysf/debug-reset-webinar)
![Downloads/week](https://npmjs.org/package/@vprok/debug-reset-webinar)
![License](https://github.com/appsolutelysf/debug-reset-webinar/blob/master/package.json)

sfdx hello:org [-n ] [-f] [-v ] [-u ] [--apiversion ] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

print a greeting and your org IDs

OPTIONS -f, --force example boolean flag -n, --name=name name to print

-u, --targetusername=targetusername username or alias for the target org; overrides default target org

-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

EXAMPLES $ sfdx hello:org --targetusername myOrg@example.com --targetdevhubusername devhub@org.com Hello world! This is org: MyOrg and I will be around until Tue Mar 20 2018! My hub org id is: 00Dxx000000001234 $ sfdx hello:org --name myname --targetusername myOrg@example.com Hello myname! This is org: MyOrg and I will be around until Tue Mar 20 2018!`

`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:orgcommand: 1. Start the inspector If you linked your plugin to the sfdx cli, call your command with thedev-suspendswitch:`sh-session $ sfdx hello:org -u myOrg@example.com --dev-suspend`Alternatively, to call your command using thebin/run script, set the NODE_OPTIONS environment variable to --inspect-brkwhen starting the debugger:`sh-session $ NODE_OPTIONS=--inspect-brk bin/run hello:org -u myOrg@example.com``

2. Set some breakpoints in your command code
3. Click on the Debug icon in the Activity Bar on the side of VS Code to open up the Debug view.
4. In the upper left hand corner of VS Code, verify that the "Attach to Remote" launch configuration has been chosen.
5. 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.
6. 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!

print a greeting and your org IDs


USAGE
  $ sfdx hello:org [-n ] [-f] [-v ] [-u ] [--apiversion ] [--json] [--loglevel 
  trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]

OPTIONS
  -f, --force                                                                       example boolean flag
  -n, --name=name                                                                   name to print

  -u, --targetusername=targetusername                                               username or alias for the target
                                                                                    org; overrides default target org

  -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|TRACE|DEBUG|INFO|WARN|ERROR|FATAL)  [default: warn] logging level for
                                                                                    this command invocation

EXAMPLES
  $ sfdx hello:org --targetusername myOrg@example.com --targetdevhubusername devhub@org.com
     Hello world! This is org: MyOrg and I will be around until Tue Mar 20 2018!
     My hub org id is: 00Dxx000000001234
  
  $ sfdx hello:org --name myname --targetusername myOrg@example.com
     Hello myname! This is org: MyOrg and I will be around until Tue Mar 20 2018!

Debugging your plugin

We recommend using the Visual Studio Code (VS Code) IDE for your plugin development. Included in the

directory of this plugin is a

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:

sh-session
$ 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:

sh-session
$ NODE_OPTIONS=--inspect-brk bin/run hello:org -u myOrg@example.com

Congrats, you are debugging!