0.0.0 • Published 5 years ago
efrontforce v0.0.0
efrontforce
efrontforce plugin
$ npm install -g efrontforce
$ sfdx COMMAND
running command...
$ sfdx (-v|--version|version)
efrontforce/0.0.0 win32-x64 node-v12.14.1
$ sfdx --help [COMMAND]
USAGE
$ sfdx COMMAND
...
sfdx efrontforce:changeset:deploy -n <string> -s <string> -t <string> [-c] [-p] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
USAGE
$ sfdx efrontforce:changeset:deploy -n <string> -s <string> -t <string> [-c] [-p] [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
OPTIONS
-c, --checkonly Déploiement en mode validation
-n, --name=name (required) Nom du change set
-p, --persist Persister le change set en locale
-s, --source=source (required) L'org source
-t, --target=target (required) L'org destination
--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 efrontforce:changeset:deploy -s MonOrgSource -t MonOrgDestination -n "MonChangeSet"
Cette commande va déployer votre change set MonChangeSet du MonOrgSource vers MonOrgDestination
$ sfdx efrontforce:changeset:deploy -s MonOrgSource -t MonOrgDestination -n "MonChangeSet" -p
Cette commande va déployer votre change set MonChangeSet du MonOrgSource vers MonOrgDestination et le persister en
locale
⚠️ attention : si il y un dossier dans votre projet porte le même nom que le change set, il sera ecrasé
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
- 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!
0.0.0
5 years ago