| commit | 0ba5e0cd4fa8a72eb8a54681030b590b0552edec | [log] [tgz] |
|---|---|---|
| author | John Ryan <ryjohn@google.com> | Fri Jun 24 10:02:07 2022 -0700 |
| committer | GitHub <noreply@github.com> | Fri Jun 24 10:02:07 2022 -0700 |
| tree | d9e64478a08964fdb47ec238c47e9f1ff2c1809b | |
| parent | 95d28128f83874107ea735932ffc2770ca5dd1a1 [diff] |
[go_router] [test-exempt] Use make-deps-path-based script for analysis and tests (#2252) * Use pub deps in go_router_builder * use make-deps-path-based in analyze steps * remove newline * add make-deps-path-based for tests * Cause go_router_builder to break, but go_router tests pass * (test) bump go_router to 4.0.1 * Revert experimental breakage * Revert go_router to 4.0.0 * Specify go_router_builder version in pubspec * bump go_router_builder version * Use path dependency overrides in example * remove dependency overrides - unsupported by make-deps-path-based * update go_router_builder/CHANGELOG.md * Change go_router_builder/example pubspec to point to pub.dev * Add separate pathified_* checks * Update go_router_builder SDK constraints Specify the same SDK constraints as go_router in go_router_builder * Use path-based dependency for go_router_builder in example * Address code review comments * add --run-on-dirty-packages to pathified test script * Use --run-on-changed-packages flag for analyze * Bypass tool_runner.sh to use --run-on-dirty-packages flag The tool_runner.sh script adds the "--packages-for-branch" flag, which can't be used with "--run-on-dirty-packages flag" https://github.com/flutter/packages/blob/main/script/tool_runner.sh#L12 * Remove unused _go_router_fake package * Format .cirrus.yml, use a shared dart_unit_tests_exceptions.yaml file * Remove redundant comment * Update CHANGELOG.md * Update .cirrus.yml
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.
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 available packages in this repository.
