Merge branch 'stable' into 'master'

전체파일 머지

See merge request !2

.vscode/settings.json

+// VSCode workspace settings that are shared among all users of this project.
+// This only affects subdirectories of this project.
+{
+    // VSCode formats files on save by default. Since Flutter source code is
+    // hand-formatted, the default settings are changed to prevent inadvertent
+    // reformatting of code.
+    "[dart]": {
+        "editor.formatOnSave": false,
+        "editor.formatOnType": false,
+        "editor.formatOnPaste": false,
+    },
+
+    "html.format.enable": false,
+    "githubPullRequests.ignoredPullRequestBranches": [
+        "master"
+    ],
+    "files.trimTrailingWhitespace": true
+}

AUTHORS

+# Below is a list of people and organizations that have contributed
+# to the Flutter project. Names should be added to the list like so:
+#
+#   Name/Organization <email address>
+#
+# Anyone who has contributed to the Flutter project in any way (not
+# limited to submitting PRs) is welcome to submit a PR to add their
+# name to this file.
+#
+# Thanks to everyone for your contributions!
+
+Google Inc.
+The Chromium Authors
+The Fuchsia Authors
+Jim Simon <jim.j.simon@gmail.com>
+Lex Berezhny <lex@damoti.com>
+Wyatt Arent <hello@wyatt.ninja>
+Michael Perrotte <mikemimik@gmail.com>
+Günter Zöchbauer <guenter@gzoechbauer.com>
+Raju Bitter <rajubitter@gmail.com>
+Michael Beckler <mcbeckler@gmail.com>
+Alexandre Ardhuin <alexandre.ardhuin@gmail.com>
+Luke Freeman <luke@goposse.com>
+Vincent Le Quéméner <eu.lequem@gmail.com>
+Mike Hoolehan <mike@hoolehan.com>
+German Saprykin <saprykin.h@gmail.com>
+Stefano Rodriguez <hlsroddy@gmail.com>
+Yusuke Konishi <yahpeycoy0403@gmail.com>
+Fredrik Simón <fredrik@fsimon.net>
+Ali Bitek <alibitek@protonmail.ch>
+Tetsuhiro Ueda <najeira@gmail.com>
+Dan Field <dfield@gmail.com>
+Noah Groß <gross@ngsger.de>
+Victor Choueiri <victor@ctrlanddev.com>
+Christian Mürtz <teraarts@t-online.de>
+Lukasz Piliszczuk <lukasz@intheloup.io>
+Felix Schmidt <felix.free@gmx.de>
+Artur Rymarz <artur.rymarz@gmail.com>
+Chema Molins <chemamolins@gmail.com>
+Stefan Mitev <mr.mitew@gmail.com>
+Jasper van Riet <jaspervanriet@gmail.com>
+Mattijs Fuijkschot <mattijs.fuijkschot@gmail.com>
+Volodymyr Lykhonis <vladimirlichonos@gmail.com>
+TruongSinh Tran-Nguyen <i@truongsinh.pro>
+Sander Dalby Larsen <srdlarsen@gmail.com>
+Marco Scannadinari <m@scannadinari.co.uk>
+Frederik Schweiger <mail@flschweiger.net>
+Martin Staadecker <machstg@gmail.com>
+Igor Katsuba <katsuba.igor@gmail.com>
+Diego Velásquez <diego.velasquez.lopez@gmail.com>
+Simon Lightfoot <simon@devangels.london>
+Sarbagya Dhaubanjar <mail@sarbagyastha.com.np>
+Rody Davis Jr <rody.davis.jr@gmail.com>
+Robin Jespersen <info@unitedpartners.de>
+Jefferson Quesado <jeff.quesado@gmail.com>
+Mark Diener <rpzrpzrpz@gmail.com>
+Alek Åström <alek.astrom@gmail.com>
+Efthymios Sarpmpanis <e.sarbanis@gmail.com>
+Cédric Wyss <cedi.wyss@gmail.com>
+Michel Feinstein <michel@feinstein.com.br>
+Michael Lee <ckmichael8@gmail.com>
+Katarina Sheremet <katarina@sheremet.ch>
+Nicolas Schneider <nioncode+git@gmail.com>
+Mikhail Zotyev <mbixjkee1392@gmail.com>
+Maria Melnik <melnikmk@gmail.com>
+Ayush Bherwani <ayush.bherwani1998@gmail.com>
+Luke Cheng <chengludev@gmail.com>
+Brian Wang <xinlei966@gmail.com>
+法的空间 <zmtzawqlp@live.com>
+CaiJingLong <cjl_spy@163.com>
+Alex Li <alexv.525.li@gmail.com>
+Ram Navan <hiramprasad@gmail.com>
+meritozh <ah841814092@gmail.com>
+Terrence Addison Tandijono(flotilla) <terrenceaddison32@gmail.com>
+YeungKC <flutter@yeungkc.com>
+Nobuhiro Tabuki <japanese.around30@gmail.com>
+nt4f04uNd <nt4f04und@gmail.com>
+Anurag Roy <anuragr9847@gmail.com>
+Andrey Kabylin <andrey@kabylin.ru>
+vimerzhao <vimerzhao@gmail.com>
+Pedro Massango <pedromassango.developer@gmail.com>
+Hidenori Matsubayashi <Hidenori.Matsubayashi@sony.com>
+Perqin Xie <perqinxie@gmail.com>
+Seongyun Kim <helloworld@cau.ac.kr>
+Ludwik Trammer <ludwik@gmail.com>
+J-P Nurmi <jpnurmi@gmail.com>
+Marian Triebe <m.triebe@live.de>
+Alexis Rouillard <contact@arouillard.fr>
+Mirko Mucaria <skogsfrae@gmail.com>
+Karol Czeryna <karol.czeryna@gmail.com>
+Callum Moffat <callum@moffatman.com>
+Koutaro Mori <koutaro.mo@gmail.com>
+Sergei Smitskoi <sergflutterdev@gmail.com>
+Casey Rogers <caseycrogers@berkeley.edu>
+Pradumna Saraf <pradumnasaraf@gmail.com>
+Kai Yu <yk3372@gmail.com>
+Denis Grafov <grafov.denis@gmail.com>
+TheOneWithTheBraid <the-one@with-the-braid.cf>
+Alberto Miola <betoman96@gmail.com>
+Twin Sun, LLC <google-contrib@twinsunsolutions.com>
+Taskulu LDA <contributions@taskulu.com>
+Jonathan Joelson <jon@joelson.co>
+Elsabe Ros <hello@elsabe.dev>
+Nguyễn Phúc Lợi <nploi1998@gmail.com>
+Jingyi Chen <jingyichen@link.cuhk.edu.cn>
+Junhua Lin <1075209054@qq.com>
+Tomasz Gucio <tgucio@gmail.com>
+Jason C.H <ctrysbita@outlook.com>
+Hubert Jóźwiak <hjozwiakdx@gmail.com>
+David Neuy <quantjump@gmail.com>
+Eli Albert <crasowas@gmail.com>
+Jan Kuß <jan@kuss.dev>
+André Sousa <andrelvsousa@gmail.com>
+Bartek Pacia <barpac02@gmail.com>
+Mike Rydstrom <m.rydstrom@gmail.com>
+Harish Anbalagan <warriorharish95668@gmail.com>
+Kim Jiun <kkimj@hanyang.ac.kr>
+LinXunFeng <linxunfeng@yeah.net>
+Sabin Neupane <sabin.neupane26@gmail.com>
+Mahdi Bagheri <1839491@gmail.com>
+Mok Kah Wai <taboosun1996@gmail.com>
+Lucas Saudon <lsaudon@gmail.com>
+Om Phatak <everythingoutdated@gmail.com>

CODEOWNERS

+# Below is a list of Flutter team members' GitHub handles who are
+# suggested reviewers for contributions to this repository.
+#
+# These names are just suggestions. It is fine to have your changes
+# reviewed by someone else.
+#
+# Use git ls-files '<pattern>' without a / prefix to see the list of matching files.
+
+/packages/flutter_tools/pubspec.yaml @christopherfujino
+/packages/flutter_tools/templates/module/ios/ @jmagman
+/packages/flutter_tools/templates/**/Podfile* @jmagman

CODE_OF_CONDUCT.md

+<!-- when updating this file also update https://github.com/flutter/.github/blob/main/CODE_OF_CONDUCT.md -->
+
+# Code of conduct
+
+The Flutter project expects Flutter's contributors to act professionally
+and respectfully. Flutter contributors are expected to maintain the safety
+and dignity of Flutter's social environments (such as GitHub and Discord).
+
+Specifically:
+
+* Respect people, their identities, their culture, and their work.
+* Be kind. Be courteous. Be welcoming.
+* Listen. Consider and acknowledge people's points before responding.
+
+Should you experience anything that makes you feel unwelcome in Flutter's
+community, please contact [conduct@flutter.dev](mailto:conduct@flutter.dev)
+or, if you prefer, directly contact someone on the project, for instance
+[Hixie](mailto:ian@hixie.ch).
+
+The Flutter project will not tolerate harassment in Flutter's
+community, even outside of Flutter's public communication channels.
+
+## Conflict resolution
+
+When multiple contributors disagree on the direction for a particular
+patch or the general direction of the project, the conflict should be
+resolved by communication. The people who disagree should get
+together, try to understand each other's points of view, and work to
+find a design that addresses everyone's concerns.
+
+This is usually sufficient to resolve issues. If you cannot come to an
+agreement, ask for the advice of a more senior member of the project.
+
+Be wary of agreement by attrition, where one person argues a point
+repeatedly until other participants give up in the interests of moving
+on. This is not conflict resolution, as it does not address everyone's
+concerns. Be wary of agreement by compromise, where two good competing
+solutions are merged into one mediocre solution. A conflict is
+addressed when the participants agree that the final solution is
+_better_ than all the conflicting proposals. Sometimes the solution is
+more work than either of the proposals. [Embrace the yak
+shave](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#lazy-programming).
+
+## Questions
+
+It's always ok to ask questions. Our systems are large, and nobody will be
+an expert in all the systems. Once you find the answer, document it in
+the first place you looked. That way, the next person will be brought
+up to speed even quicker.
+
+!["I try not to make fun of people for admitting they don't know things, because for each thing 'everyone knows' by the time they're adults, every day there are, on average, 10,000 people in the US hearing about it for the first time. If I make fun of people, I train them not to tell me when they have those moments. And I miss out on the fun." "Diet coke and mentos thing? What's that?" "Oh, man! We're going to the grocery store." "Why?" "You're one of today's lucky 10,000."](https://imgs.xkcd.com/comics/ten_thousand.png)
+
+Source: _[xkcd, May 2012](https://xkcd.com/1053/)_

CONTRIBUTING.md

+<!-- when editing this file also update https://github.com/flutter/.github/blob/main/CONTRIBUTING.md -->
+
+Contributing to Flutter
+=======================
+
+_tl;dr: join [Discord](https://github.com/flutter/flutter/wiki/Chat), be [courteous](CODE_OF_CONDUCT.md), follow the steps below to set up a development environment; if you stick around and contribute, you can [join the team](https://github.com/flutter/flutter/wiki/Contributor-access) and get commit access._
+
+Welcome
+-------
+
+We invite you to join the Flutter team, which is made up of volunteers and sponsored folk alike!
+There are many ways to contribute, including writing code, filing issues on GitHub, helping people
+on our mailing lists, our chat channels, or on Stack Overflow, helping to triage, reproduce, or
+fix bugs that people have filed, adding to our documentation,
+doing outreach about Flutter, or helping out in any other way.
+
+We grant commit access (which includes full rights to the issue
+database, such as being able to edit labels) to people who have gained
+our trust and demonstrated a commitment to Flutter. For more details
+see the [Contributor access](https://github.com/flutter/flutter/wiki/Contributor-access)
+page on our wiki.
+
+We communicate primarily over GitHub and [Discord](https://github.com/flutter/flutter/wiki/Chat).
+
+Before you get started, we encourage you to read these documents which describe some of our community norms:
+
+1. [Our code of conduct](CODE_OF_CONDUCT.md), which stipulates explicitly
+   that everyone must be gracious, respectful, and professional. This
+   also documents our conflict resolution policy and encourages people
+   to ask questions.
+
+2. [Values](https://github.com/flutter/flutter/wiki/Values),
+   which talks about what we care most about.
+
+Helping out in the issue database
+---------------------------------
+
+Triage is the process of going through bug reports and determining if they are valid, finding out
+how to reproduce them, catching duplicate reports, and generally making our issues list
+useful for our engineers.
+
+If you want to help us triage, you are very welcome to do so!
+
+1. Join the #hackers-triage [Discord channel](https://github.com/flutter/flutter/wiki/Chat).
+
+2. Read [our code of conduct](CODE_OF_CONDUCT.md), which stipulates explicitly
+   that everyone must be gracious, respectful, and professional. If you're helping out
+   with triage, you are representing the Flutter team, and so you want to make sure to
+   make a good impression!
+
+3. Help out as described in our wiki: https://github.com/flutter/flutter/wiki/Triage
+   You won't be able to add labels at first, so instead start by trying to
+   do the other steps, e.g. trying to reproduce the problem and asking for people to
+   provide enough details that you can reproduce the problem, pointing out duplicates,
+   and so on. Chat on the #hackers-triage channel to let us know what you're up to!
+
+4. Familiarize yourself with our
+   [issue hygiene](https://github.com/flutter/flutter/wiki/Issue-hygiene) wiki page,
+   which covers the meanings of some important GitHub labels and
+   milestones.
+
+5. Once you've been doing this for a while, someone will invite you to the flutter-hackers
+   team on GitHub and you'll be able to add labels too. See the
+   [contributor access](https://github.com/flutter/flutter/wiki/Contributor-access) wiki
+   page for details.
+
+
+Quality Assurance
+-----------------
+
+One of the most useful tasks, closely related to triage, is finding and filing bug reports. Testing
+beta releases, looking for regressions, creating test cases, adding to our test suites, and
+other work along these lines can really drive the quality of the product up. Creating tests
+that increase our test coverage, writing tests for issues others have filed, all these tasks
+are really valuable contributions to open source projects.
+
+If this interests you, you can jump in and submit bug reports without needing anyone's permission!
+The #quality-assurance channel on our [Discord server](https://github.com/flutter/flutter/wiki/Chat)
+is a good place to talk about what you're doing. We're especially eager for QA testing when
+we announce a beta release. See https://github.com/flutter/flutter/wiki/Quality-Assurance for
+more details.
+
+If you want to contribute test cases, you can also submit PRs. See the next section
+for how to set up your development environment, or ask in #hackers-test on Discord.
+
+> As a personal side note, this is exactly the kind of work that first got me into open
+> source. I was a Quality Assurance volunteer on the Mozilla project, writing test cases for
+> browsers, long before I wrote a line of code for any open source project. —Hixie
+
+
+Developing for Flutter
+----------------------
+
+If you would prefer to write code, you may wish to start with our list of good first issues for [Flutter](https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) or for [Flutter DevTools](https://github.com/flutter/devtools/labels/good%20first%20issue). See the respective sections below for further instructions.
+
+### Framework and Engine
+
+To develop for Flutter, you will eventually need to become familiar
+with our processes and conventions. This section lists the documents
+that describe these methodologies. The following list is ordered: you
+are strongly recommended to go through these documents in the order
+presented.
+
+1. [Setting up your engine development environment](https://github.com/flutter/flutter/wiki/Setting-up-the-Engine-development-environment),
+   which describes the steps you need to configure your computer to
+   work on Flutter's engine. If you only want to write code for the
+   Flutter framework, you can skip this step. Flutter's engine mainly
+   uses C++, Java, and Objective-C.
+
+2. [Setting up your framework development environment](https://github.com/flutter/flutter/wiki/Setting-up-the-Framework-development-environment),
+   which describes the steps you need to configure your computer to
+   work on Flutter's framework. Flutter's framework mainly uses Dart.
+
+3. [Tree hygiene](https://github.com/flutter/flutter/wiki/Tree-hygiene),
+   which covers how to land a PR, how to do code review, how to
+   handle breaking changes, how to handle regressions, and how to
+   handle post-commit test failures.
+
+4. [Our style guide](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo),
+   which includes advice for designing APIs for Flutter, and how to
+   format code in the framework.
+
+5. [Flutter design doc template](https://flutter.dev/go/template),
+   which should be used when proposing a new technical design.  This is a good
+   practice to do before coding more intricate changes.
+   See also our [guidance for writing design docs](https://github.com/flutter/flutter/wiki/Design-Documents).
+
+[![How to contribute to Flutter](https://img.youtube.com/vi/4yBgOBAOx_A/0.jpg)](https://www.youtube.com/watch?v=4yBgOBAOx_A)
+
+In addition to the documents, there is a video linked above on **How to contribute to Flutter**
+from the [Flutter](https://youtube.com/c/flutterdev) YouTube channel,
+there are many pages on [our Wiki](https://github.com/flutter/flutter/wiki/),
+and an article [Contributing to Flutter: Getting Started](https://medium.com/@ayushbherwani/contributing-to-flutter-getting-started-a0db68cbcd5b)
+on Medium that may be of interest. For a curated list of pages see the sidebar
+on the wiki's home page. They are more or less listed in order of importance.
+
+### DevTools
+
+Contributing code to Dart & Flutter DevTools may be a good place to start if you are
+looking to dip your toes into contributing with a relatively low-cost setup or if you
+are generally excited about improving the Dart & Flutter developer experience.
+
+Please see the DevTools [CONTRIBUTING.md](https://github.com/flutter/devtools/blob/master/CONTRIBUTING.md)
+guide to get started.
+
+Outreach
+--------
+
+If your interests lie in the direction of developer relations and developer outreach,
+whether advocating for Flutter, answering questions in fora like
+[Stack Overflow](https://stackoverflow.com/questions/tagged/flutter?sort=Newest&filters=NoAnswers,NoAcceptedAnswer&edited=true)
+or [Reddit](https://www.reddit.com/r/flutterhelp/new/?f=flair_name%3A%22OPEN%22),
+or creating content for our [documentation](https://docs.flutter.dev/)
+or sites like [YouTube](https://www.youtube.com/results?search_query=flutter&sp=EgQIAxAB),
+the best starting point is to join the #hackers-devrel [Discord channel](https://github.com/flutter/flutter/wiki/Chat).
+From there, you can describe what you're interested in doing, and go ahead and do it!
+As others become familiar with your work, they may have feedback, be interested in
+collaborating, or want to coordinate their efforts with yours.
+
+
+API documentation
+-----------------
+
+Another great area to contribute in is sample code and API documentation. If this is an area that interests you, join our
+[Discord](https://github.com/flutter/flutter/wiki/Chat) server and introduce yourself on the #hackers-deverl, #hackers-framework,
+or #hackers-engine channels, describing your area of interest. As our API docs are integrated into our source code, see the
+"developing for Flutter" section above for a guide on how to set up your developer environment.
+
+To contribute API documentation, an excellent command of the English language is particularly helpful, as is a careful attention to detail.
+We have a [whole section in our style guide](https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#documentation-dartdocs-javadocs-etc)
+that you should read before you write API documentation. It includes notes on the "Flutter Voice", such as our word and grammar conventions.
+
+In general, a really productive way to improve documentation is to use Flutter and stop any time you have a question: find the answer, then
+document the answer where you first looked for it.
+
+We also keep [a list of areas that need better API documentation](https://github.com/flutter/flutter/issues?q=is%3Aopen+is%3Aissue+label%3A%22d%3A+api+docs%22+sort%3Areactions-%2B1-desc).
+In many cases, we have written down what needs to be said in the relevant issue, we just haven't gotten around to doing it!
+
+We're especially eager to add sample code and diagrams to our API documentation. Diagrams are generated from Flutter code that
+draws to a canvas, and stored in a [special repository](https://github.com/flutter/assets-for-api-docs/#readme). It can be a lot of fun
+to create new diagrams for the API docs.
+
+
+Releases
+--------
+
+If you are interested in participating in our release process, which may involve writing release notes and blog posts, coordinating the actual
+generation of binaries, updating our release tooling, and other work of that nature, then reach out on the #hackers-releases
+channel of our [Discord](https://github.com/flutter/flutter/wiki/Chat) server.
+
+
+Social events in the contributor community
+------------------------------------------
+
+Finally, one area where you could have a lot of impact is in contributing to social interactions among the Flutter contributor community itself.
+This could take the form of organizing weekly video chats on our Discord, or planning tech talks from contributors, for example.
+If this is an area that is of interest to you, please join our [Discord](https://github.com/flutter/flutter/wiki/Chat) and ping Hixie on the #hackers
+channel!

LICENSE

+Copyright 2014 The Flutter Authors. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without modification,
+are permitted provided that the following conditions are met:
+
+    * Redistributions of source code must retain the above copyright
+      notice, this list of conditions and the following disclaimer.
+    * Redistributions in binary form must reproduce the above
+      copyright notice, this list of conditions and the following
+      disclaimer in the documentation and/or other materials provided
+      with the distribution.
+    * Neither the name of Google Inc. nor the names of its
+      contributors may be used to endorse or promote products derived
+      from this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
+ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PATENT_GRANT

+Google hereby grants to you a perpetual, worldwide, non-exclusive,
+no-charge, royalty-free, irrevocable (except as stated in this
+section) patent license to make, have made, use, offer to sell, sell,
+import, transfer, and otherwise run, modify and propagate the contents
+of this implementation, where such license applies only to those
+patent claims, both currently owned by Google and acquired in the
+future, licensable by Google that are necessarily infringed by this
+implementation. This grant does not include claims that would be
+infringed only as a consequence of further modification of this
+implementation. If you or your agent or exclusive licensee institute
+or order or agree to the institution of patent litigation or any other
+patent enforcement activity against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that this
+implementation constitutes direct or contributory patent infringement,
+or inducement of patent infringement, then any patent rights granted
+to you under this License for this implementation shall terminate as
+of the date such litigation is filed.

README.md

+<a href="https://flutter.dev/">
+  <h1 align="center">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://storage.googleapis.com/cms-storage-bucket/6e19fee6b47b36ca613f.png">
+      <img alt="Flutter" src="https://storage.googleapis.com/cms-storage-bucket/c823e53b3a1a7b0d36a9.png">
+    </picture>
+  </h1>
+</a>
+
+[![Flutter CI Status](https://flutter-dashboard.appspot.com/api/public/build-status-badge?repo=flutter)](https://flutter-dashboard.appspot.com/#/build?repo=flutter)
+[![Discord badge][]][Discord instructions]
+[![Twitter handle][]][Twitter badge]
+[![codecov](https://codecov.io/gh/flutter/flutter/branch/master/graph/badge.svg?token=11yDrJU2M2)](https://codecov.io/gh/flutter/flutter)
+[![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/5631/badge)](https://bestpractices.coreinfrastructure.org/projects/5631)
+[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/flutter/flutter/badge)](https://deps.dev/project/github/flutter%2Fflutter)
+[![SLSA 1](https://slsa.dev/images/gh-badge-level1.svg)](https://slsa.dev)
+
+Flutter is Google's SDK for crafting beautiful, fast user experiences for
+mobile, web, and desktop from a single codebase. Flutter works with existing
+code, is used by developers and organizations around the world, and is free and
+open source.
+
+## Documentation
+
+* [Install Flutter](https://flutter.dev/get-started/)
+* [Flutter documentation](https://docs.flutter.dev/)
+* [Development wiki](https://github.com/flutter/flutter/wiki)
+* [Contributing to Flutter](https://github.com/flutter/flutter/blob/master/CONTRIBUTING.md)
+
+For announcements about new releases, follow the
+[flutter-announce@googlegroups.com](https://groups.google.com/forum/#!forum/flutter-announce)
+mailing list. Our documentation also tracks [breaking
+changes](https://docs.flutter.dev/release/breaking-changes) across releases.
+
+## Terms of service
+
+The Flutter tool may occasionally download resources from Google servers. By
+downloading or using the Flutter SDK, you agree to the Google Terms of Service:
+https://policies.google.com/terms
+
+For example, when installed from GitHub (as opposed to from a prepackaged
+archive), the Flutter tool will download the Dart SDK from Google servers
+immediately when first run, as it is used to execute the `flutter` tool itself.
+This will also occur when Flutter is upgraded (e.g. by running the `flutter
+upgrade` command).
+
+## About Flutter
+
+We think Flutter will help you create beautiful, fast apps, with a productive,
+extensible and open development model, whether you're targeting iOS or Android,
+web, Windows, macOS, Linux or embedding it as the UI toolkit for a platform of
+your choice.
+
+### Beautiful user experiences
+
+We want to enable designers to deliver their full creative vision without being
+forced to water it down due to limitations of the underlying framework.
+Flutter's [layered architecture] gives you control over every pixel on the
+screen and its powerful compositing capabilities let you overlay and animate
+graphics, video, text, and controls without limitation. Flutter includes a full
+[set of widgets][widget catalog] that deliver pixel-perfect experiences whether
+you're building for iOS ([Cupertino]) or other platforms ([Material]), along with
+support for customizing or creating entirely new visual components.
+
+<p align="center"><img src="https://github.com/flutter/website/blob/main/src/assets/images/docs/homepage/reflectly-hero-600px.png?raw=true" alt="Reflectly hero image"></p>
+
+### Fast results
+
+Flutter is fast. It's powered by hardware-accelerated 2D graphics
+libraries like [Skia] (that underpins Chrome and Android) and
+[Impeller]. We architected Flutter to
+support glitch-free, jank-free graphics at the native speed of your device.
+
+Flutter code is powered by the world-class [Dart platform], which enables
+compilation to 32-bit and 64-bit ARM machine code for iOS and Android,
+JavaScript and WebAssembly for the web, as well as Intel x64 and ARM
+for desktop devices.
+
+<p align="center"><img src="https://github.com/flutter/website/blob/main/src/assets/images/docs/homepage/dart-diagram-small.png?raw=true" alt="Dart diagram"></p>
+
+### Productive development
+
+Flutter offers [stateful hot reload][Hot reload], allowing you to make changes to your code
+and see the results instantly without restarting your app or losing its state.
+
+[![Hot reload animation][]][Hot reload]
+
+### Extensible and open model
+
+Flutter works with any development tool (or none at all), and also includes
+editor plug-ins for both [Visual Studio Code] and [IntelliJ / Android Studio].
+Flutter provides [tens of thousands of packages][Flutter packages] to speed your
+development, regardless of your target platform. And accessing other native code
+is easy, with support for both FFI ([on Android][Android FFI], [on iOS][iOS FFI],
+[on macOS][macOS FFI], and [on Windows][Windows FFI]) as well as
+[platform-specific APIs][platform channels].
+
+Flutter is a fully open-source project, and we welcome contributions.
+Information on how to get started can be found in our
+[contributor guide](CONTRIBUTING.md).
+
+[flutter.dev]: https://flutter.dev
+[Discord instructions]: https://github.com/flutter/flutter/wiki/Chat
+[Discord badge]: https://img.shields.io/discord/608014603317936148?logo=discord
+[Twitter handle]: https://img.shields.io/twitter/follow/flutterdev.svg?style=social&label=Follow
+[Twitter badge]: https://twitter.com/intent/follow?screen_name=flutterdev
+[layered architecture]: https://docs.flutter.dev/resources/inside-flutter
+[architectural overview]: https://docs.flutter.dev/resources/architectural-overview
+[widget catalog]: https://flutter.dev/widgets/
+[Cupertino]: https://docs.flutter.dev/development/ui/widgets/cupertino
+[Material]: https://docs.flutter.dev/development/ui/widgets/material
+[Skia]: https://skia.org/
+[Dart platform]: https://dart.dev/
+[Hot reload animation]: https://github.com/flutter/website/blob/main/src/assets/images/docs/tools/android-studio/hot-reload.gif?raw=true
+[Hot reload]: https://docs.flutter.dev/development/tools/hot-reload
+[Visual Studio Code]: https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
+[IntelliJ / Android Studio]: https://plugins.jetbrains.com/plugin/9212-flutter
+[Flutter packages]: https://pub.dev/flutter
+[Android FFI]: https://docs.flutter.dev/development/platform-integration/android/c-interop
+[iOS FFI]: https://docs.flutter.dev/development/platform-integration/ios/c-interop
+[macOS FFI]: https://docs.flutter.dev/development/platform-integration/macos/c-interop
+[Windows FFI]: https://docs.flutter.dev/development/platform-integration/windows/building#integrating-with-windows
+[platform channels]: https://docs.flutter.dev/development/platform-integration/platform-channels
+[interop example]: https://github.com/flutter/flutter/tree/master/examples/platform_channel
+[Impeller]: https://docs.flutter.dev/perf/impeller

bin/dart

+#!/usr/bin/env bash
+# Copyright 2014 The Flutter Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# ---------------------------------- NOTE ---------------------------------- #
+#
+# Please keep the logic in this file consistent with the logic in the
+# `dart.bat` script in the same directory to ensure that Flutter & Dart continue
+# to work across all platforms!
+#
+# -------------------------------------------------------------------------- #
+
+set -e
+
+# Needed because if it is set, cd may print the path it changed to.
+unset CDPATH
+
+# On Mac OS, readlink -f doesn't work, so follow_links traverses the path one
+# link at a time, and then cds into the link destination and find out where it
+# ends up.
+#
+# The returned filesystem path must be a format usable by Dart's URI parser,
+# since the Dart command line tool treats its argument as a file URI, not a
+# filename. For instance, multiple consecutive slashes should be reduced to a
+# single slash, since double-slashes indicate a URI "authority", and these are
+# supposed to be filenames. There is an edge case where this will return
+# multiple slashes: when the input resolves to the root directory. However, if
+# that were the case, we wouldn't be running this shell, so we don't do anything
+# about it.
+#
+# The function is enclosed in a subshell to avoid changing the working directory
+# of the caller.
+function follow_links() (
+  cd -P "$(dirname -- "$1")"
+  file="$PWD/$(basename -- "$1")"
+  while [[ -h "$file" ]]; do
+    cd -P "$(dirname -- "$file")"
+    file="$(readlink -- "$file")"
+    cd -P "$(dirname -- "$file")"
+    file="$PWD/$(basename -- "$file")"
+  done
+  echo "$file"
+)
+
+PROG_NAME="$(follow_links "${BASH_SOURCE[0]}")"
+BIN_DIR="$(cd "${PROG_NAME%/*}" ; pwd -P)"
+SHARED_NAME="$BIN_DIR/internal/shared.sh"
+OS="$(uname -s)"
+
+# If we're on Windows, invoke the batch script instead to get proper locking.
+if [[ $OS =~ MINGW.* || $OS =~ CYGWIN.* || $OS =~ MSYS.* ]]; then
+  exec "${BIN_DIR}/dart.bat" "$@"
+fi
+
+# To define `shared::execute()` function
+source "$SHARED_NAME"
+
+shared::execute "$@"

bin/dart.bat

+@ECHO off
+REM Copyright 2014 The Flutter Authors. All rights reserved.
+REM Use of this source code is governed by a BSD-style license that can be
+REM found in the LICENSE file.
+
+REM ---------------------------------- NOTE ----------------------------------
+REM
+REM Please keep the logic in this file consistent with the logic in the
+REM `dart` script in the same directory to ensure that Flutter & Dart continue to
+REM work across all platforms!
+REM
+REM --------------------------------------------------------------------------
+
+SETLOCAL
+
+FOR %%i IN ("%~dp0..") DO SET FLUTTER_ROOT=%%~fi
+
+REM Include shared scripts in shared.bat
+SET shared_bin=%FLUTTER_ROOT%/bin/internal/shared.bat
+CALL "%shared_bin%"
+
+SET cache_dir=%FLUTTER_ROOT%\bin\cache
+SET dart_sdk_path=%cache_dir%\dart-sdk
+SET dart=%dart_sdk_path%\bin\dart.exe
+
+SET exit_with_errorlevel=%FLUTTER_ROOT%/bin/internal/exit_with_errorlevel.bat
+
+REM Chaining the call to 'dart' and 'exit' with an ampersand ensures that
+REM Windows reads both commands into memory once before executing them. This
+REM avoids nasty errors that may otherwise occur when the dart command (e.g. as
+REM part of 'flutter upgrade') modifies this batch script while it is executing.
+REM
+REM Do not use the CALL command in the next line to execute Dart. CALL causes
+REM Windows to re-read the line from disk after the CALL command has finished
+REM regardless of the ampersand chain.
+"%dart%" %* & "%exit_with_errorlevel%"

bin/flutter

+#!/usr/bin/env bash
+# Copyright 2014 The Flutter Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# ---------------------------------- NOTE ---------------------------------- #
+#
+# Please keep the logic in this file consistent with the logic in the
+# `flutter.bat` script in the same directory to ensure that Flutter continues
+# to work across all platforms!
+#
+# -------------------------------------------------------------------------- #
+
+set -e
+
+# To debug the tool, you can uncomment the following lines to enable debug
+# mode and set an observatory port:
+# FLUTTER_TOOL_ARGS="--enable-asserts $FLUTTER_TOOL_ARGS"
+# FLUTTER_TOOL_ARGS="$FLUTTER_TOOL_ARGS --observe=65432"
+
+# Needed because if it is set, cd may print the path it changed to.
+unset CDPATH
+
+# On Mac OS, readlink -f doesn't work, so follow_links traverses the path one
+# link at a time, and then cds into the link destination and find out where it
+# ends up.
+#
+# The returned filesystem path must be a format usable by Dart's URI parser,
+# since the Dart command line tool treats its argument as a file URI, not a
+# filename. For instance, multiple consecutive slashes should be reduced to a
+# single slash, since double-slashes indicate a URI "authority", and these are
+# supposed to be filenames. There is an edge case where this will return
+# multiple slashes: when the input resolves to the root directory. However, if
+# that were the case, we wouldn't be running this shell, so we don't do anything
+# about it.
+#
+# The function is enclosed in a subshell to avoid changing the working directory
+# of the caller.
+function follow_links() (
+  cd -P "$(dirname -- "$1")"
+  file="$PWD/$(basename -- "$1")"
+  while [[ -h "$file" ]]; do
+    cd -P "$(dirname -- "$file")"
+    file="$(readlink -- "$file")"
+    cd -P "$(dirname -- "$file")"
+    file="$PWD/$(basename -- "$file")"
+  done
+  echo "$file"
+)
+
+PROG_NAME="$(follow_links "${BASH_SOURCE[0]}")"
+BIN_DIR="$(cd "${PROG_NAME%/*}" ; pwd -P)"
+SHARED_NAME="$BIN_DIR/internal/shared.sh"
+OS="$(uname -s)"
+
+# If we're on Windows, invoke the batch script instead to get proper locking.
+if [[ $OS =~ MINGW.* || $OS =~ CYGWIN.* || $OS =~ MSYS.* ]]; then
+  exec "${BIN_DIR}/flutter.bat" "$@"
+fi
+
+# To define `shared::execute()` function
+source "$SHARED_NAME"
+
+shared::execute "$@"

bin/flutter.bat

+@ECHO off
+REM Copyright 2014 The Flutter Authors. All rights reserved.
+REM Use of this source code is governed by a BSD-style license that can be
+REM found in the LICENSE file.
+
+REM ---------------------------------- NOTE ----------------------------------
+REM
+REM Please keep the logic in this file consistent with the logic in the
+REM `flutter` script in the same directory to ensure that Flutter & Dart continue to
+REM work across all platforms!
+REM
+REM --------------------------------------------------------------------------
+
+SETLOCAL
+
+REM To debug the tool, you can uncomment the following line to enable debug mode:
+REM SET FLUTTER_TOOL_ARGS="--enable-asserts %FLUTTER_TOOL_ARGS%"
+
+FOR %%i IN ("%~dp0..") DO SET FLUTTER_ROOT=%%~fi
+
+REM If available, add location of bundled mingit to PATH
+SET mingit_path=%FLUTTER_ROOT%\bin\mingit\cmd
+IF EXIST "%mingit_path%" SET PATH=%PATH%;%mingit_path%
+
+REM We test if Git is available on the Host as we run git in shared.bat
+REM  Test if the flutter directory is a git clone, otherwise git rev-parse HEAD would fail
+IF NOT EXIST "%flutter_root%\.git" (
+  ECHO Error: The Flutter directory is not a clone of the GitHub project.
+  ECHO        The flutter tool requires Git in order to operate properly;
+  ECHO        to set up Flutter, run the following command:
+  ECHO        git clone -b stable https://github.com/flutter/flutter.git
+  EXIT 1
+)
+
+REM Include shared scripts in shared.bat
+SET shared_bin=%FLUTTER_ROOT%\bin\internal\shared.bat
+CALL "%shared_bin%"
+
+SET flutter_tools_dir=%FLUTTER_ROOT%\packages\flutter_tools
+SET cache_dir=%FLUTTER_ROOT%\bin\cache
+SET snapshot_path=%cache_dir%\flutter_tools.snapshot
+SET dart_sdk_path=%cache_dir%\dart-sdk
+SET dart=%dart_sdk_path%\bin\dart.exe
+
+SET exit_with_errorlevel=%FLUTTER_ROOT%/bin/internal/exit_with_errorlevel.bat
+
+REM Chaining the call to 'dart' and 'exit' with an ampersand ensures that
+REM Windows reads both commands into memory once before executing them. This
+REM avoids nasty errors that may otherwise occur when the dart command (e.g. as
+REM part of 'flutter upgrade') modifies this batch script while it is executing.
+REM
+REM Do not use the CALL command in the next line to execute Dart. CALL causes
+REM Windows to re-read the line from disk after the CALL command has finished
+REM regardless of the ampersand chain.
+"%dart%" --disable-dart-dev --packages="%flutter_tools_dir%\.dart_tool\package_config.json" %FLUTTER_TOOL_ARGS% "%snapshot_path%" %* & "%exit_with_errorlevel%"

bin/internal/README.md

+## Flutter SDK dependency versions
+
+The files in this directory specifies pinned versions of various
+dependencies of the flutter SDK.
+
+The `bin/internal/engine.version` file controls which version of the
+Flutter engine to use. The file contains the commit hash of a commit
+in the <https://github.com/flutter/engine> repository. That hash must
+have successfully been compiled on
+<https://build.chromium.org/p/client.flutter/> and had its artifacts
+(the binaries that run on Android and iOS, the compiler, etc)
+successfully uploaded to Google Cloud Storage.
+
+The `/bin/internal/engine.merge_method` file controls how we merge a
+pull request created by the engine auto-roller. If it's `squash`,
+there's only one commit for a pull request no matter how many engine
+commits there are inside that pull request. If it's `rebase`, the
+number of commits in the framework is equal to the number of engine
+commits in the pull request. The latter method makes it easier to
+detect regressions but costs more test resources.
+
+The `bin/internal/flutter_packages.version` file specifies the version
+of the `flutter/packages` repository to be used for testing. The
+`flutter/packages` repository isn't an upstream dependency of
+`flutter/flutter`; it is only used as part of the test suite for
+verification, and the pinned version here makes sure that tests are
+deterministic at each `flutter/flutter` commit.

bin/internal/canvaskit.version

+61aeJQ9laGfEFF_Vlc_u0MCkqB6xb2hAYHRBxKH-Uw4C

bin/internal/engine.merge_method

+squash

bin/internal/engine.version

+55eae6864b296dd9f43b2cc7577ec256e5c32a8d

bin/internal/exit_with_errorlevel.bat

+@ECHO off
+REM Copyright 2014 The Flutter Authors. All rights reserved.
+REM Use of this source code is governed by a BSD-style license that can be
+REM found in the LICENSE file.
+
+REM A script to exit caller script with the last status code.
+REM This can be used with ampersand without `SETLOCAL ENABLEDELAYEDEXPANSION`.
+REM
+REM To use this script like `exit`, do not use with the CALL command.
+REM Without CALL, this script can exit caller script, but with CALL,
+REM this script returns back to caller and does not exit caller.
+
+exit /B %ERRORLEVEL%