generated from salesforcecli/plugin-template
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: message naming conventions from linter, node: imports (#770)
- Loading branch information
Showing
13 changed files
with
211 additions
and
243 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -39,23 +39,23 @@ For more information about user limits, defaults, and other considerations when | |
|
||
<%= config.bin %> <%= command.id %> --definition-file config/project-user-def.json email=[email protected] generatepassword=true --set-unique-username | ||
|
||
# flags.alias.summary | ||
# flags.set-alias.summary | ||
|
||
Set an alias for the created username to reference in other CLI commands. | ||
|
||
# flags.definitionfile.summary | ||
# flags.definition-file.summary | ||
|
||
File path to a user definition file for customizing the new user. | ||
|
||
# flags.definitionfile.description | ||
# flags.definition-file.description | ||
|
||
The user definition file uses JSON format and can include any Salesforce User sObject field and Salesforce DX-specific options. See https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_users_def_file.htm for more information. | ||
|
||
# flags.setuniqueusername.summary | ||
# flags.set-unique-username.summary | ||
|
||
Force the username, if specified in the definition file or at the command line, to be unique by appending the org ID. | ||
|
||
# flags.setuniqueusername.description | ||
# flags.set-unique-username.description | ||
|
||
The new user’s username must be unique across all Salesforce orgs and in the form of an email address. If you let this command generate a username for you, it's guaranteed to be unique. If you specify an existing username in a definition file, the command fails. Set this flag to force the username to be unique; as a result, the username might be different than what you specify in the definition file. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,10 +16,10 @@ For scratch orgs, the list includes any users you've created with the "org creat | |
|
||
<%= config.bin %> <%= command.id %> --target-org [email protected] | ||
|
||
# flags.target-hub.summary | ||
# flags.target-dev-hub.summary | ||
|
||
Username or alias of the Dev Hub org. | ||
|
||
# flags.target-hub.deprecation | ||
# flags.target-dev-hub.deprecation | ||
|
||
The --target-dev-hub flag is deprecated and is no longer used by this command. The flag will be removed in API version 57.0 or later. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.