Brian Wilkerson
1bf8019253
Change-Id: I5db4055b2fe950c09cdfe95c3f08270bf3f5df7c Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/156380 Reviewed-by: Jaime Wren <jwren@google.com> Reviewed-by: Devon Carew <devoncarew@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@google.com>
21 lines
724 B
Markdown
21 lines
724 B
Markdown
# Design Principles
|
|
|
|
The purpose of this document is to capture the design principles that should be
|
|
followed when designing new commands or updating existing ones. The goal is to
|
|
ensure that the dartdev tool provides a consistent UX.
|
|
|
|
## Status
|
|
|
|
This is a work in progress. At the moment we are just capturing the ideas that
|
|
are coming out of discussions. They will need to be organized and more fully
|
|
documented at some point.
|
|
|
|
## Command Arguments
|
|
|
|
### Default Target
|
|
|
|
If the command cannot have side effects (such as analyze) then the argument for
|
|
what to operate on should default to the CWD, but if the command can have side
|
|
effects (such as format or fix) then the argument for what to operate on should
|
|
be required.
|