firka/flutter
firka/flutter
5
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README.md to clarify who flutter-dev is for and what the trade-offs are (#153947)

Browse Source 
*Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.*

*List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.*

*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
This commit is contained in:
Seth Ladd 2024-08-22 10:49:50 -07:00 committed by GitHub
parent ef098c2aa4
commit 1b234858f2
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
packages/flutter_tools/README.md
View File

@ -26,12 +26,18 @@ $ dart bin/flutter_tools.dart
``` ```
followed by command-line arguments, as usual. followed by command-line arguments, as usual.
As a convenience, you can also use the `bin/flutter-dev` script: As a convenience for folks developing the `flutter` tool itself,
you can also use the `bin/flutter-dev` script:
```shell ```shell
# Assuming flutter/bin is on your PATH # Assuming flutter/bin is on your PATH
$ flutter-dev $ flutter-dev
``` ```
Note: `flutter-dev` is identical to `flutter`, except it does not
use a cached on-disk snapshot. In other words, it will be significantly
slower but you will not need to forget (remember?) to delete the cached
snapshot.
### Running the analyzer ### Running the analyzer
To run the analyzer on Flutter Tools, in this directory run: To run the analyzer on Flutter Tools, in this directory run: