Skip to content

[packages] Federate plugin READMEs #182772

@stuartmorgan-g

Description

@stuartmorgan-g

When we fully federated all of our plugins (moving the platform implementations out of the app-facing package), we mostly didn't change the READMEs, which has resulted in a lot of cases where README discussion of platform-implementation-specific code/logic/behaviors/etc. are in a different package that the actual code controlling that behavior. This causes things to get out of sync because we can't atomically change the code and the README documentation. We've done some ad-hoc fixes over time in some plugins, but we really need to go ahead and do it for all of our plugins so that we aren't dealing with this as tech debt when individual cases come up (e.g., #163779).

google_sign_in is an example of how we want this to work.

  • camera
  • file_selector
  • google_maps_flutter
  • google_sign_in
  • image_picker
  • in_app_purchase
  • local_auth
  • path_provider (the table of supported methods is arguably more useful when centralized, but it's not maintainable this way)
  • pointer_interceptor
  • quick_actions
  • shared_preferences
  • url_launcher
  • video_player
  • webview_flutter

Metadata

Metadata

Labels

P2Important issues not at the top of the work listpackageflutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions