-
Notifications
You must be signed in to change notification settings - Fork 21
Design Guidelines Sub Actions
Shane McLaughlin edited this page Aug 31, 2023
·
1 revision
Sub-actions are additional verbs that qualify the primary action. Sub-actions are optional and used only when necessary. For example, in the command sf project deploy start
, the sub-action start
qualifies what the command project deploy
will do.
A sub-action can also be a followup action related to a previous asynchronous action. For example, sf data query
with the --async
flag starts a bulk query. You can then use sf data query resume --use-most-recent
to "resume" that query later.
- Sub-actions are optional.
- Sub-actions are verbs.
sf project deploy start
sf project deploy preview
sf project deploy report
sf data query resume
© Copyright 2024 Salesforce.com, inc. All rights reserved. Various trademarks held by their respective owners.
- Quick Intro to Developing sf Plugins
- Get Started: Create Your First Plugin
- Design Guidelines
- Code Your Plugin
- Debug Your Plugin
- Write Useful Messages
- Test Your Plugin
- Maintain Your Plugin
- Integrate Your Plugin With the Doctor Command
- Migrate Plugins Built for sfdx
- Conceptual Overview of Salesforce CLI