Skip to content

feat(share_plus): Eligible to share files with specific application via package name #3531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

chandrabezzo
Copy link

@chandrabezzo chandrabezzo commented Mar 27, 2025

Description

Now, we can share to specific package name with fill package name of the destination app.

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • I titled the PR using Conventional Commits.
  • I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
  • All existing and new tests are passing.
  • The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
  • No, this is not a breaking change.

hadiisantoso and others added 7 commits September 19, 2023 09:30
…cific-package

# Conflicts:
#	packages/share_plus/share_plus/android/src/main/kotlin/dev/fluttercommunity/plus/share/MethodCallHandler.kt
#	packages/share_plus/share_plus/example/lib/main.dart
#	packages/share_plus/share_plus/example/pubspec.yaml
#	packages/share_plus/share_plus/pubspec.yaml
#	packages/share_plus/share_plus_platform_interface/lib/method_channel/method_channel_share.dart
@chandrabezzo chandrabezzo changed the title feat: Eligible to share files with specific application via package name feat(share_plus): Eligible to share files with specific application via package name Mar 27, 2025
@miquelbeltran
Copy link
Member

This is quite a large PR, and it is not following the contributor guidelines (e.g. you are modifying changelogs, pubspec, etc.) unfortunately also this is not compatible with the upcoming refactor of share_plus (which I should work on someday).
I'd prefer if you could create a ticket first requesting this feature and see if it could be incorporated into the share_plus refactor. Thanks for your time, and for understanding!

@chandrabezzo
Copy link
Author

Ok, I have created ticket #3541 @miquelbeltran

@chandrabezzo
Copy link
Author

In the future, I think better to set request changes first instead of directly close the pull request. So, I can changes following your guideline @miquelbeltran.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants