Design Guidelines Patterns

• --async Flag for events that are long running and happening on server level.
  • Example: sf org create sandbox --async
  • Example: sf data query --async
• Providing User Feedback for Long Running Commands
• Interactive commands should provide a spinner
• Long-running commands should always provide an id to report back on
• Multiple resources should have a default
• Lists should be presented as tables
• Including and outputting files or directories should use the following flags --output-file, —output-dir, —input-file, --input-dir