tree 36bc10f7f2537c79c193f242c78668be8c5201c8
parent 5ea96e51de83ae5cfcfecf5ae4af15fdd5f8c9b8
author stuartmorgan <stuartmorgan@google.com> 1629471504 -0700
committer GitHub <noreply@github.com> 1629471504 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhH8MQCRBK7hj4Ov3rIwAAi7AIADHFoXJbrUezB9TTejv+z78R
 mwZANwd4VJLQ539h3kAophswAjcyFtolplu1mpqhVIRSmY1SOexfsGKPpa5gbAB6
 CVmtlGZVYDuTATuGBKfHfsaiZfTtcfzHF9KN6/YraY8HoXWr5kT83ZcthO/0UirJ
 6TWEy+5LN/Dv5digozxIme46hrl9KS5jGDHBTef3R5uu1bPD25+B4f+DKthyESc0
 Em53xI79CxPpJ7EDCnZ9Z8cDjO7JHUh0PZWpuktg0krk+iTRVbZPYOwWt/fHhItS
 e4lO9Kfw6VkvSm75dPLRQkoWwMRksArizGwMlUTP5LENsv7wlQwg/92aEtxaO3s=
 =yTVH
 -----END PGP SIGNATURE-----
 

Fix and test for 'implements' pubspec entry (#4242)

The federated plugin spec calls for implementation packages to include an `implements` entry in the `plugins` section of the `pubspec.yaml` indicating what app-facing package it implements. Most of the described behaviors of the `flutter` tool aren't implemented yet, and the pub.dev features have `default_plugin` as a backstop, so we haven't noticed that they are mostly missing (or in one case, incorrect).

To better future-proof the plugins, and to provide a better example to people looking at our plugins as examples of federation, this adds a CI check to make sure that we are correctly adding it, and fixes all of the missing/incorrect values it turned up.

Fixes https://github.com/flutter/flutter/issues/88222