flutter/packages/flutter_tools/test
stuartmorgan 2dd8cb1ca2
Don't use example folder as a project type signal (#97157)
The code to generate platform files used to use the presence of an
'example' folder to determine whether or not a project was a plugin (in
which case that generation is bypassed). Later, robust detection was
added based on the pubspec.yaml `plugin` key, but the old check was left
in place. This creates false positives where people who add an example
folder to their app project start getting mysterious failures.

Since the pubspec check is definitive, there's no reason to continue to
use the presence of `example` as an indicator at all.

Fixes https://github.com/flutter/flutter/issues/87007
2022-01-24 19:28:38 -08:00
..
commands.shard Take screenshot when drive fails to start app or test (#96828) 2022-01-19 21:35:19 -08:00
data "Migrate" dummy packages to null safety (#84013) 2021-06-04 22:14:03 -07:00
general.shard Don't use example folder as a project type signal (#97157) 2022-01-24 19:28:38 -08:00
integration.shard [flutter_tools] support files in flutter analyze #96231 (#97021) 2022-01-24 17:10:16 -08:00
src Revert "FFI plugins (#94101)" (#96122) 2022-01-04 08:09:12 -08:00
web.shard Enable no_leading_underscores_for_local_identifiers (#96422) 2022-01-21 14:43:59 -08:00