Zzhaoxin24742file_selector
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[ci] Update minimums for 3.13 stable (#4731) - Updates the N-1 and N-2 analysis bot configs to 3.7 and 3.10 - Updates the minimum allowed SDK to 3.7, since that's now the earliest we have any testing for. - Updates all packages to Flutter 3.7/Dart 2.19 as a minimum. - In packages where we hadn't released since the last minimum version bump, I removed the previous line from the #NEXT section to make it less confusing when we do release. Per https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#version this does not update any package versions. | 3 年前 | |
[various] Update Pigeon in Swift plugins (#4461) Updates pigeon in all of our Swift plugins, to ensure that they have the fix for https://github.com/flutter/flutter/issues/129283 Fixes https://github.com/flutter/flutter/issues/129536 | 3 年前 | |
[various] Update Pigeon in Swift plugins (#4461) Updates pigeon in all of our Swift plugins, to ensure that they have the fix for https://github.com/flutter/flutter/issues/129283 Fixes https://github.com/flutter/flutter/issues/129536 | 3 年前 | |
[file_selector] Switch to Pigeon for macOS (#6902) * Initial pigeon definition * Update Dart, and add Dart test coverage * Update Swift and native tests * Version bump * Format * Revert SDK change | 3 年前 | |
[various] Update Pigeon in Swift plugins (#4461) Updates pigeon in all of our Swift plugins, to ensure that they have the fix for https://github.com/flutter/flutter/issues/129283 Fixes https://github.com/flutter/flutter/issues/129536 | 3 年前 | |
[file_selector] Add macOS support (#4381) Brings file_selector_macos into flutter/plugins from FDE, with the following changes: - Refactored slightly to allow for unit tests of almost all of the native code - Added native unit test coverage - Translated to Swift, to follow repo conventions for macOS plugins - Added an in-package example (almost an exact duplicate of the app-facing version, but written against the platform interface, as is our current practice) - Moved to an in-package method channel. As part of that, moved the flattening of type groups from Swift to Dart. Does not currently include native UI tests to allow for end-to-end testing (since Flutter integration tests can't be used). They should be added later (they are currently blocked on https://github.com/flutter/flutter/issues/90673), but the unit tests give substantial coverage, making it substantially better to move the plugin now to get those tests running. macOS portion of https://github.com/flutter/flutter/issues/70221 | 4 年前 | |
[file_selector] Add macOS support (#4381) Brings file_selector_macos into flutter/plugins from FDE, with the following changes: - Refactored slightly to allow for unit tests of almost all of the native code - Added native unit test coverage - Translated to Swift, to follow repo conventions for macOS plugins - Added an in-package example (almost an exact duplicate of the app-facing version, but written against the platform interface, as is our current practice) - Moved to an in-package method channel. As part of that, moved the flattening of type groups from Swift to Dart. Does not currently include native UI tests to allow for end-to-end testing (since Flutter integration tests can't be used). They should be added later (they are currently blocked on https://github.com/flutter/flutter/issues/90673), but the unit tests give substantial coverage, making it substantially better to move the plugin now to get those tests running. macOS portion of https://github.com/flutter/flutter/issues/70221 | 4 年前 | |
[file_selector] Add macOS support (#4381) Brings file_selector_macos into flutter/plugins from FDE, with the following changes: - Refactored slightly to allow for unit tests of almost all of the native code - Added native unit test coverage - Translated to Swift, to follow repo conventions for macOS plugins - Added an in-package example (almost an exact duplicate of the app-facing version, but written against the platform interface, as is our current practice) - Moved to an in-package method channel. As part of that, moved the flattening of type groups from Swift to Dart. Does not currently include native UI tests to allow for end-to-end testing (since Flutter integration tests can't be used). They should be added later (they are currently blocked on https://github.com/flutter/flutter/issues/90673), but the unit tests give substantial coverage, making it substantially better to move the plugin now to get those tests running. macOS portion of https://github.com/flutter/flutter/issues/70221 | 4 年前 | |
file_selector Signed-off-by: zhaoxin24742 <zhaoxin24742@openvalley.net> | 2 年前 | |
[file_selector] Add macOS support (#4381) Brings file_selector_macos into flutter/plugins from FDE, with the following changes: - Refactored slightly to allow for unit tests of almost all of the native code - Added native unit test coverage - Translated to Swift, to follow repo conventions for macOS plugins - Added an in-package example (almost an exact duplicate of the app-facing version, but written against the platform interface, as is our current practice) - Moved to an in-package method channel. As part of that, moved the flattening of type groups from Swift to Dart. Does not currently include native UI tests to allow for end-to-end testing (since Flutter integration tests can't be used). They should be added later (they are currently blocked on https://github.com/flutter/flutter/issues/90673), but the unit tests give substantial coverage, making it substantially better to move the plugin now to get those tests running. macOS portion of https://github.com/flutter/flutter/issues/70221 | 4 年前 | |
[various] Clarify endorsement in READMEs (#3404) [various] Clarify endorsement in READMEs | 3 年前 | |
file_selector Signed-off-by: zhaoxin24742 <zhaoxin24742@openvalley.net> | 2 年前 |
file_selector_macos
The macOS implementation of file_selector.
Usage
This package is endorsed, which means you can simply use file_selector
normally. This package will be automatically included in your app when you do,
so you do not need to add it to your pubspec.yaml.
However, if you import this package to use any of its APIs directly, you
should add it to your pubspec.yaml as usual.
Entitlements
You will need to add an entitlement for either read-only access:
<key>com.apple.security.files.user-selected.read-only</key>
<true/>
or read/write access:
<key>com.apple.security.files.user-selected.read-write</key>
<true/>
depending on your use case.