091f0ff99e
additions: - root package files need a header - added ci step - performance increases (executes in like 15s now) - added README.md to the data directory - cleaned up --v=1 log ## 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]. <!-- 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
VSCode Workspace
This is the tools and the template used for updating //engine.code-workspace.
VSCode uses a custom version of JSONC for their config files, those config files don't provide any mechanism for reducing redundancy. Since the engine has a lot of test targets, without that mechanism it can get very unwieldy. YAML does however support ways to reduce redundancy, namely anchors.
Updating //engine.code-workspace
./refresh.sh
Backporting //engine.code-workspace
If something is accidentally introduced into //engine.code-workspace without editing the YAML file here there are tools that can be used to more easily fix that.
./merge.sh
Since JSON doesn't support anchors some work may be needed to resolve any conflicts that happen when merging. These aren't necessary to use the VSCode workspace, just to edit them.
Requirements
The refresh.sh and merge.sh tools require certain tools to be present on
your PATH. They can be installed on macos with homebrew.
json5- A variant of JSON that is a superset of the JSON variant that VSCode uses. It's used to strip away comments and trailing commas.yq- This is a tool for manipulating yaml files. It can convert back and forth from YAML to YAML and merge YAML files.