@siddharatha/dxutils
v0.0.10
Published
Additional utilities to support vscode utilities
Downloads
71
Readme
dxutils
Additional utilities to support vscode utilities
$ 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]
@siddharatha/dxutils <%= command.id %> [-d <integer>] [-a] [-c] [-u <string>] [--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal]
@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 [email protected]
Hello myname
Calculating packages
$ sfdx dxutils:eventlogs -u [email protected] -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 [email protected]
Hello myname
Calculating packages
$ sfdx dxutils:pull -u [email protected] -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:
- Start the inspector
If you linked your plugin to the sfdx cli, call your command with the dev-suspend
switch:
$ sfdx hello:org -u [email protected] --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 [email protected]
- Set some breakpoints in your command code
- Click on the Debug icon in the Activity Bar on the side of VS Code to open up the Debug view.
- In the upper left hand corner of VS Code, verify that the "Attach to Remote" launch configuration has been chosen.
- 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.
- 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!