Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

Conversation

@stuartmorgan-g
Copy link
Contributor

Eliminates the remaining uses of the deprecated method for returning the
example for a package that assumed there must be only one example,
migrating the remaining uses to support multi-example.

Fixes one unit test that was accidentally testing the wrong failure case
due to a copy/paste mistake, noticed while updating tests for this
change.

Pre-launch Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I read the Tree Hygiene wiki page, which explains my responsibilities.
  • I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
  • I signed the CLA.
  • The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
  • I listed at least one issue that this PR fixes in the description above.
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
  • I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is test-exempt.
  • All existing and new tests are passing.

Eliminates the remaining uses of the deprecated method for returning the
example for a package that assumed there must be only one example,
migrating the remaining uses to support multi-example.

Fixes one unit test that was accidentally testing the wrong failure case
due to a copy/paste mistake, noticed while updating tests for this
change.
@stuartmorgan-g stuartmorgan-g requested a review from ditman May 3, 2022 14:24
@stuartmorgan-g
Copy link
Contributor Author

I forgot this was still here, and noticed it while fixing getExamples in the previous PR.

Copy link
Member

@ditman ditman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great improvement for the tooling. I wonder how a multi-example package will score in pub (it'll probably get some points deducted because example/lib/main.dart doesn't exist?)

@stuartmorgan-g
Copy link
Contributor Author

Great improvement for the tooling. I wonder how a multi-example package will score in pub (it'll probably get some points deducted because example/lib/main.dart doesn't exist?)

It's a documented convention, so in theory they should support it: https://dart.dev/tools/pub/package-layout#examples

I checked rfw since it's a published multi-example package, and it has an example/README.md explaining the examples which satisfies scoring. Maybe that's what all multi-example packages should do and they ding packages that don't.

@stuartmorgan-g stuartmorgan-g added the waiting for tree to go green (Use "autosubmit") This PR is approved and tested, but waiting for the tree to be green to land. label May 3, 2022
@fluttergithubbot fluttergithubbot merged commit e40abaa into flutter:main May 3, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request May 4, 2022
mauricioluz pushed a commit to mauricioluz/plugins that referenced this pull request Jan 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

waiting for tree to go green (Use "autosubmit") This PR is approved and tested, but waiting for the tree to be green to land.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants