text
stringlengths 1
372
|
|---|
<topic_end>
|
<topic_start>
|
installation and setup
|
follow the set up an editor instructions to
|
install the dart and flutter extensions
|
(also called plugins).
|
<topic_end>
|
<topic_start>
|
updating the extension
|
updates to the extensions are shipped on a regular basis.
|
by default, VS code automatically updates extensions when
|
updates are available.
|
to install updates yourself:
|
<topic_end>
|
<topic_start>
|
creating projects
|
there are a couple ways to create a new project.
|
<topic_end>
|
<topic_start>
|
creating a new project
|
to create a new flutter project from the flutter
|
starter app template:
|
go to view >
|
command palette….
|
you can also press ctrl / cmd +
|
shift + p.
|
<topic_end>
|
<topic_start>
|
opening a project from existing source code
|
to open an existing flutter project:
|
go to file > open.
|
you can also press ctrl / cmd + o
|
<topic_end>
|
<topic_start>
|
editing code and viewing issues
|
the flutter extension performs code analysis.
|
the code analysis can:
|
navigate to type declarations
|
find type usages.
|
view all current source code problems.
|
<topic_end>
|
<topic_start>
|
running and debugging
|
info note
|
you can debug your app in a couple of ways.
|
the instructions below describe features available in VS code.
|
for information on using launching DevTools, see
|
running DevTools from VS code in the DevTools docs.
|
start debugging by clicking run > start debugging
|
from the main IDE window, or press f5.
|
<topic_end>
|
<topic_start>
|
selecting a target device
|
when a flutter project is open in VS code,
|
you should see a set of flutter specific entries in the status bar,
|
including a flutter SDK version and a
|
device name (or the message no devices):
|
info note
|
the flutter extension automatically selects the last device connected.
|
however, if you have multiple devices/simulators connected, click
|
device in the status bar to see a pick-list
|
at the top of the screen. select the device you want to use for
|
running or debugging.
|
are you developing for macOS or iOS remotely using
|
visual studio code remote? if so, you might need to manually
|
unlock the keychain. for more information, see this
|
question on StackExchange.
|
<topic_end>
|
<topic_start>
|
run app without breakpoints
|
go to run > start without debugging.
|
you can also press ctrl + f5.
|
<topic_end>
|
<topic_start>
|
run app with breakpoints
|
click run > start debugging.
|
you can also press f5.
|
the status bar turns orange to show you are in a debug session.
|
<topic_end>
|
<topic_start>
|
run app in debug, profile, or release mode
|
flutter offers many different build modes to run your app in.
|
you can read more about them in flutter’s build modes.
|
open the launch.json file in VS code.
|
if you don’t have a launch.json file:
|
go to view > run.
|
you can also press ctrl / cmd +
|
shift + d
|
the run and debug panel displays.
|
click create a launch.json file.
|
in the configurations section,
|
change the flutterMode property to
|
the build mode you want to target.
|
for example, if you want to run in debug mode,
|
your launch.json might look like this:
|
run the app through the run panel.
|
<topic_end>
|
<topic_start>
|
fast edit and refresh development cycle
|
flutter offers a best-in-class developer cycle enabling you
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.