metadata-coverage-report
xmlformat =========
Last updated a year ago by gearset .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install metadata-coverage-report 
SYNC missed versions from official npm registry.

xmlformat

Version CircleCI Appveyor CI Codecov Greenkeeper Known Vulnerabilities Downloads/week License

$ npm install -g metadata-coverage-report
$ metadata-coverage-report COMMAND
running command...
$ metadata-coverage-report (-v|--version|version)
metadata-coverage-report/0.5.0 darwin-x64 node-v9.4.0
$ metadata-coverage-report --help [COMMAND]
USAGE
  $ metadata-coverage-report COMMAND
...

metadata-coverage-report metadata:coverage

Prints the coverage report from your org

USAGE
  $ metadata-coverage-report metadata:coverage

OPTIONS
  -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)   logging level for this command invocation

EXAMPLES
  $ sfdx metadata:coverage --targetusername myOrg@example.com
    
       ─────────────────────────────────────  ─────  ─────────────────────────────────  
  ──────────────────────────────────────
       AccessControlPolicy                    ✓      ✓ Expanded Source Tracking (Beta)  ✓ Requires Package without a 
  Namespace
       AccountSettings                        ✓      ✓                                  ✘
  
  $ sfdx metadata:coverage --targetusername myOrg@example.com --json

See code: src/commands/metadata/coverage.ts

metadata-coverage-report metadata:format

Formats your SFDX metadata

USAGE
  $ metadata-coverage-report metadata:format

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

EXAMPLE
  $ sfdx metadata:format
       Formatted 10 files

See code: src/commands/metadata/format.ts

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

  • 0.5.0                                ...           latest (a year ago)

1 Versions

  • 0.5.0                                ...           a year ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 1
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |