[Request]: Add legal copyright from Windows exe etc. to PackageInfo
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- desktop-dev, mobile-dev
Research direction
Start with the package_info_plus platform implementations and the PackageInfo class; the issue does not name specific files or tests. Trace how Windows executable metadata is currently exposed, then determine how the proposed Android and iOS copyright sources fit the API. Done means PackageInfo exposes the requested legal-copyright value with platform behavior defined.
Written by the indexing model from the issue text.
Description
Plugin
package_info_plus
Use case
I am using the package_info_plus-Addon to retrieve a PackageInfo instance and fill with this the properties of the AboutDialog. Currently, I use the following properties to fill the following properties:
- appName -> applicationName
- 'v${version} (Build ${buildNumber})' -> applicationVersion
and I am missing the legal copyright-String from the executable of the app to use that for the applicationLegalese property. Can you please add to extract the LegalCopyright property from the Windows application executable and provide that value in a field within the PackageInfo class?
Proposal
The plugin should also extract the value from the LegalCopyright property of the Windows executable and provide that as a field in the PackageInfo class. For Android, the contents for that field may come from a copyright text file (see https://ash12rai-weblearning.medium.com/copyright-profiles-android-studio-e476f6613274). For iOS, the copyright text may come from https://developer.apple.com/documentation/BundleResources/Information-Property-List/NSHumanReadableCopyright.
- Dominant language
- Dart
- Stars
- 1.9k
- Forks
- 1.3k
- Avg merge
- 6d 16h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluttercommunity/plus_plugins
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
fluttercommunity/plus_plugins#3994 ·
Maintainers usually reply within 1 day
-
[package_info_plus]: Use Flutter's compile-time build name/number on web instead of version.jsonOpen
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
fluttercommunity/plus_plugins#3989 ·
Maintainers usually reply within 1 day
-
enhancement triage
Difficulty 4/5 3-5 days Newbie friendliness 55/100
fluttercommunity/plus_plugins#3976 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
fluttercommunity/plus_plugins#3974 · 1 reaction ·
Maintainers usually reply within 1 day
-
enhancement triage
Difficulty 5/5 Over a week Newbie friendliness 48/100
fluttercommunity/plus_plugins#3973 ·
Maintainers usually reply within 1 day
All issues in fluttercommunity/plus_plugins
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
atsign-foundation/at_server#2832 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
flutter/agent-plugins#244 · 1 comment ·