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

[image_picker] Federate mobile implementations#5100

Merged
fluttergithubbot merged 13 commits intoflutter:mainfrom
stuartmorgan-g:federate-image-picker-mobile
Apr 4, 2022
Merged

[image_picker] Federate mobile implementations#5100
fluttergithubbot merged 13 commits intoflutter:mainfrom
stuartmorgan-g:federate-image-picker-mobile

Conversation

@stuartmorgan-g
Copy link
Copy Markdown
Contributor

Temporarily marks image_picker as unpublishable to allow the implementations to be moved, rather than copied and deleted, in order to better preserve git history. A follow-up PR will restore it to publishable form.

Part of flutter/flutter#68498

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.

Comment thread packages/image_picker/image_picker_android/example/README.md Outdated
@@ -0,0 +1,67 @@
def localProperties = new Properties()
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This seems copy and pasted across examples, can we share this easily?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I don't think there's any reasonable way for us to share native app boilerplate across examples. Especially since over time the dependencies (at the end) could reasonably diverge.

And while this is a duplicate in practice, it's also almost identical to what flutter create would have made for us if we'd made the new example from scratch instead.


@DartIntegrationTest
@RunWith(FlutterTestRunner.class)
public class FlutterActivityTest {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do we need this? It doesn't seem to be doing anything interesting. Is it boilerplate to help future tests? Maybe we could add an example assertion?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

It's boilerplate to run the Dart integration tests in the native harness. The @RunWith(FlutterTestRunner.class) is what does the real work here.

Comment thread packages/image_picker/image_picker_ios/example/README.md Outdated
Comment on lines +13 to +14
# When depending on this package from a real application you should use:
# image_picker_ios: ^x.y.z
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This stock comment doesn't seem correct, they should depend on image_picker no?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

If someone is explicitly depending on the image_picker_ios package, as the example is doing, they should do it like this.

That's not usually what people should do, but nothing in the implementation examples is what people should usually do with a federated plugin. Usually people just use the app-facing package, and would look at the app-facing package's example.

(The implementation package examples are almost entirely for development and test-running purposes. At some point we should maybe batch-update the README boilerplate we use in them to make that more explicit.)

@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 Apr 4, 2022
@fluttergithubbot
Copy link
Copy Markdown

This pull request is not suitable for automatic merging in its current state.

  • This commit is not mergeable and has conflicts. Please rebase your PR and fix all the conflicts.

@fluttergithubbot fluttergithubbot removed 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 Apr 4, 2022
@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 Apr 4, 2022
@fluttergithubbot fluttergithubbot merged commit 7b94e2f into flutter:main Apr 4, 2022
engine-flutter-autoroll added a commit to engine-flutter-autoroll/flutter that referenced this pull request Apr 5, 2022
@stuartmorgan-g stuartmorgan-g deleted the federate-image-picker-mobile branch April 19, 2022 17:35
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

p: image_picker platform-android platform-ios 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.

4 participants