Star9
3
代码
代码
Issues
Pull Requests
项目讨论
Wiki
分析
Star9
3
GGitHubrun_ios_tests: Allow running from any directory (#190822)
a57db01c创建于 28 天前历史提交
文件最后提交记录最后更新时间
benchmarks
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
ci
Replace the rest of the references to `flutter/engine` with `flutter/flutter` (#182938) Fixes: #167478 ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
6 个月前
contributing
Add note about gclient sync network failures and workaround (#183794) <!-- Thanks for filing a pull request! Reviewers are typically assigned within a week of filing a request. To learn more about code review, see our documentation on Tree Hygiene: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md --> Adds a note to the engine setup guide about potential network-related failures during `gclient sync` and suggests using `--no-history` as a workaround. Fixes #141087 ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [X] I read the [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [X] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [X] I signed the [CLA]. - [X] I listed at least one issue that this PR fixes in the description above. - [X] I updated/added relevant documentation (doc comments with `///`). - [X] I added new tests to check the change I am making, or this PR is [test-exempt]. - [X] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [X] All existing and new tests are passing. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [AI contribution guidelines]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
5 个月前
impeller
docs: update Impeller advanced blend docs for framebuffer fetch (#185457) ## Description The advanced blend section of `blending.md` described a three-step cost (end render pass → copy backdrop → blit intermediary) that is no longer accurate on Metal and Vulkan, where framebuffer fetch is now the default. ### Changes - **`docs/engine/impeller/docs/blending.md`**: Rewrites the cost model for advanced blends to describe both code paths: - **Framebuffer fetch supported** (Metal / Vulkan default): no render pass end, no backdrop copy, no intermediary blit — the shader reads the backdrop directly from the framebuffer. Only the source snapshot is required. Still more expensive than a pipeline blend, but significantly cheaper than the legacy path. - **Framebuffer fetch not supported** (some OpenGL ES devices): the original three-step path still applies. Fixes https://github.com/flutter/flutter/issues/144004 Co-authored-by: gaaclarke <30870216+gaaclarke@users.noreply.github.com>
3 个月前
monorepo
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
rbe
Use full goto.google.com hostname for go/ links (#184679) It is best practice to use the full hostname, because it works in certain situations where go/ does not.
4 个月前
release
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
testing
run_ios_tests: Allow running from any directory (#190822) Previously `run_ios_tests.sh` only worked when invoked from `engine/src/flutter` which, to be fair, is what the READMEs tell you to do but there's no reason we need to force that, and we don't for other tests like run_tests.py. This is mostly just post-monorepo-merge cleanup. Two separate things depended on the working directory: * The wrapper was resolving `SCRIPT_DIR` from `BASH_SOURCE` but still passed the Dart entrypoint as a relative path, so the VM would report `No such file or directory`. * `run_ios_tests.dart` called `Engine.tryFindWithin()`, which defaults to the current directory and only walks upward. From the repo root `engine/src` is below the starting point, so the search fails and the script exits with `Must be run from within the engine repository.` Both now resolve from the script's own location, so the documented invocation keeps working and but invoking from any other directory works too. The Dart side matches the existing usage in `tools/header_guard_check/lib/header_guard_check.dart:162`. Also fixed up the READMEs, which had a few other issues... one if which was that I forgot to update them in #190818. No test changes because this *is* test changes. <!-- Thanks for filing a pull request! Reviewers are typically assigned within a week of filing a request. To learn more about code review, see our documentation on Tree Hygiene: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md --> ## Pre-launch Checklist - [X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [X] I read the [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [X] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [X] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [X] I signed the [CLA]. - [ ] I listed at least one issue that this PR fixes in the description above. - [X] I updated/added relevant documentation (doc comments with `///`). - [X] I added new tests to check the change I am making, or this PR is [test-exempt]. - [X] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [X] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. If this change needs to override an active code freeze, provide a comment explaining why. The code freeze workflow can be overridden by code reviewers. See pinned issues for any active code freezes with guidance. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [AI contribution guidelines]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
28 天前
Crashes.md
Update android symbolication instructions (#181267) Update the instructions: 1. new instructions for getting symbols out of libflutter.so 2. remove line about building unstripped - the local and hosted versions all default in all cases to unstripped Fixes https://github.com/flutter/flutter/issues/163249 --------- Co-authored-by: Gray Mackall <mackall@google.com> Co-authored-by: Reid Baker <1063596+reidbaker@users.noreply.github.com>
6 个月前
Custom-Flutter-Engine-Embedders.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Custom-Flutter-Engine-Embedding-in-AOT-Mode.md
Replace References to `flutter/engine` with `flutter/flutter` (#182600) towards: #167478 this should fix most of the references to `flutter/engine`(aside from PRs of course). ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [ ] I listed at least one issue that this PR fixes in the description above. - [ ] I updated/added relevant documentation (doc comments with `///`). - [ ] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
6 个月前
Debugging-the-engine.md
Delete obsolete link in Debugging-the-engine.md (#185703) Delete obsolete link in Debugging-the-engine.md The file this links to was removed in https://github.com/flutter/flutter/pull/184357, so let's remove the corresponding docs reference. No issue filed for trivial docs change. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [ ] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [AI contribution guidelines]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#ai-contribution-guidelines [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
4 个月前
Engine-disk-footprint.md
updates docs for flutter engine footprint (#176217) ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [x] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md
10 个月前
Engine-specific-Service-Protocol-extensions.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Flutter's-modes.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Flutter-Android-Engine-Flags.md
[Android] Add integration test for setting engine flags via the manifest (#182241) Adds integration tests for setting engine flags via the manifest for Flutter Android apps: https://github.com/flutter/flutter/pull/182522. Technically, a continuation of https://github.com/flutter/flutter/pull/178383. Additionally: 1. Wires up `--test-flag` added in https://github.com/flutter/flutter/pull/182522 so I can test command line flag specification taking precedence over manifest flag specification in debug mode only. 2. Fixes documentation/test bug of my previous claim that developers do not need to specify a manifest metadata value for keys/flags that do not take arguments in the format of `--flag=value` or `--flag=value1,value2,...`. This is false; metadata requires a key-value or key-resource pair (see [documentation proof](https://developer.android.com/guide/topics/manifest/meta-data-element#:~:text=receiver%3E%0A%3Cservice%3E-,description%3A,-A%20name%2Dvalue)). 3. Refactors devicelab util method for adding metadata to the app manifest to a central location. ## Pre-launch Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [Tree Hygiene] wiki page, which explains my responsibilities. - [x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement]. - [x] I signed the [CLA]. - [x] I listed at least one issue that this PR fixes in the description above. - [x] I updated/added relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or this PR is [test-exempt]. - [x] I followed the [breaking change policy] and added [Data Driven Fixes] where supported. - [ ] All existing and new tests are passing. If you need help, consider asking for advice on the #hackers-new channel on [Discord]. **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed. <!-- Links --> [Contributor Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview [Tree Hygiene]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md [test-exempt]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#tests [Flutter Style Guide]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md [Features we expect every widget to implement]: https://github.com/flutter/flutter/blob/main/docs/contributing/Style-guide-for-Flutter-repo.md#features-we-expect-every-widget-to-implement [CLA]: https://cla.developers.google.com/ [flutter/tests]: https://github.com/flutter/tests [breaking change policy]: https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#handling-breaking-changes [Discord]: https://github.com/flutter/flutter/blob/main/docs/contributing/Chat.md [Data Driven Fixes]: https://github.com/flutter/flutter/blob/main/docs/contributing/Data-driven-Fixes.md --------- Co-authored-by: jesswrd <jesswon@google.com>
4 个月前
Flutter-engine-operation-in-AOT-Mode.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Image-Codecs-in-the-Flutter-Engine.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Life-of-a-Flutter-Frame.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
README.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Supporting-legacy-platforms.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Using-Sanitizers-with-the-Flutter-Engine.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
Using-the-Dart-Development-Service-(DDS)-and-Flutter-DevTools-with-a-custom-Flutter-Engine-Embedding.md
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
app_anatomy.svg
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
dart_split_aot_compilation.svg
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
deferred_components_architecture.svg
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
deferred_components_call_lifecycle.svg
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
flutter_overview.svg
chore: move engine docs out of engine/ and into docs/ (#175195) Moving docs to be co-located with other docs + updating links. This has the benefit of not including docs in engine content hash semantics.
11 个月前
README

This is an index of team-facing documentation for the flutter/engine team.