@siddharatha/dxutils
Additional utilities to support vscode utilities
Last updated a month ago by siddharatha .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @siddharatha/dxutils 
SYNC missed versions from official npm registry.

dxutils

Additional utilities to support vscode utilities

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

$ npm install -g @siddharatha/dxutils
$ @siddharatha/dxutils COMMAND
running command...
$ @siddharatha/dxutils (-v|--version|version)
@siddharatha/dxutils/0.0.10 darwin-x64 node-v12.10.0
$ @siddharatha/dxutils --help [COMMAND]
USAGE
  $ @siddharatha/dxutils COMMAND
...

@siddharatha/dxutils <%= command.id %> [-d <string>] [-t <string>] [-e <string>] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

Assign something man

USAGE
  $ @siddharatha/dxutils dxutils:eventlogs [-d <string>] [-t <string>] [-e <string>] [-u <string>] [--apiversion 
  <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

OPTIONS
  -d, --dateliteral=dateliteral                   Enter Date
  -e, --eventtypes=eventtypes                     Enter EventTypes
  -t, --targetdir=targetdir                       Enter targetDIR
  -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

EXAMPLES
  $ sfdx dxutils:eventlogs --targetusername myOrg@example.com
           Hello myname
           Calculating packages
  $ sfdx dxutils:eventlogs -u myOrg@example.com -d THIS_WEEK -e LightningPageView
           Hello myname
           Calculating packages ...
           You have 130 metadata types in your org I can scan

See code: src/commands/dxutils/eventlogs.ts

@siddharatha/dxutils <%= command.id %> [-d <integer>] [-a] [-c] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]

Pull changes from your connected org and generate an xml or autodownload metadata based on last modified date

USAGE
  $ @siddharatha/dxutils dxutils:pull [-d <integer>] [-a] [-c] [-u <string>] [--apiversion <string>] [--json] 
  [--loglevel trace|debug|info|warn|error|fatal]

OPTIONS
  -a, --autodownload                              AutoDownload the files using sfdx force:source:retrieve

  -c, --autoclean                                 Automatically clean the files that are downloaded with sfdx
                                                  dxutils:pull

  -d, --days=days                                 Please select the number of days we need to specify for getting org
                                                  details

  -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

EXAMPLES
  $ sfdx dxutils:pull --targetusername myOrg@example.com
           Hello myname
           Calculating packages
  $ sfdx dxutils:pull -u myOrg@example.com -a
           Hello myname
           Calculating packages ...
           You have 130 metadata types in your org I can scan

See code: src/commands/dxutils/pull.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.0.10                                ...           latest (a month ago)

11 Versions

  • 0.0.10                                ...           a month ago
  • 0.0.9                                ...           7 months ago
  • 0.0.8                                ...           7 months ago
  • 0.0.7                                ...           7 months ago
  • 0.0.6                                ...           7 months ago
  • 0.0.5                                ...           7 months ago
  • 0.0.4                                ...           7 months ago
  • 0.0.3                                ...           8 months ago
  • 0.0.2                                ...           8 months ago
  • 0.0.1                                ...           8 months ago
  • 0.0.0                                ...           8 months ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 34
Dependencies (13)
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |