commit | bff47a3f0e3d128d002bca58f2f05c012bc88f27 | [log] [tgz] |
---|---|---|
author | stuartmorgan-g <stuartmorgan@google.com> | Wed Aug 27 20:54:39 2025 |
committer | GitHub <noreply@github.com> | Wed Aug 27 20:54:39 2025 |
tree | 965e95b0e568a264f6d6ee16feff0b7465733ce4 | |
parent | c905585a8846e11b1b85ce0060e99a09fab377c1 [diff] | |
parent | ffd7a9da62c63a52941fdc158c1191fd588a2b0c [diff] |
[google_fonts] Initial import (#9895) Initial import of [`google_fonts`](https://github.com/material-foundation/flutter-packages/tree/7ef4a67e00f3f9503079753b890416dc3aeced56/packages/google_fonts) As with previous package imports, this is a history graft that will be landed as a merge rather than a squash, to preserve commit history. My changes are all visible as follow-up commits to the initial merge commit, but to summarize: - Updated the package metadata (version, changelog, repo links, etc.) - Updated the min SDK version to follow our policy - Autoformated for the new SDK version - Fixed (or in some cases, ignored) violations of our stricter analysis options - Adopted the README code excerpts system - Adopted the standard repo license format, per repo policy - Removed the use of `cider` to auto-generate changelog updates during generation, to remove the third-party dependency - Added a suffix to the generated code, and adds a repo-level rule to ignore that suffix during analysis - Added repo-level allowance for protobuf (google-owned) and mustache_template (pinned, with allowance explanation) - Removed example/test/unit_test.dart, which failed in CI (it wasn't being run in the source repo's CI) and appeared to be demonstrating an anti-pattern (trying to load fonts via the network in a unit test). - Updated example/android/ to use the new build style
This repo is a companion repo to the main flutter repo. It contains the source code for Flutter's first-party packages (i.e., packages developed by the core Flutter team). Check the packages
directory to see all packages.
These packages are also available on pub.
Please file any issues, bugs, or feature requests in the main flutter repo. Issues pertaining to this repository are labeled “package”.
If you wish to contribute a new package to the Flutter ecosystem, please see the documentation for developing packages. You can store your package source code in any GitHub repository (the present repo is only intended for packages developed by the core Flutter team). Once your package is ready you can publish to the pub repository.
If you wish to contribute a change to any of the existing packages in this repo, please review our contribution guide, and send a pull request.
These are the packages hosted in this repository: