文件最后提交记录最后更新时间
Update repo for 3.32 stable (#9311) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.32 stable release (except the first one, as the stable roller has already landed).1 年前
[various] Update iOS/macOS Pigeon versions (#8226) Updates iOS and macOS plugin implementations that were still using Pigeon 10/11 to the latest version (22). This picks up some minor improvements to serialization, as well as newer dependencies that can avoid resolver issues in flutter/flutter tests (see linked issue). Most of this PR is auto-generated via the repo tool's update-dependency command; only minor manual updates were required (mostly to test code). Fixes https://github.com/flutter/flutter/issues/1598031 年前
[various] Update iOS/macOS Pigeon versions (#8226) Updates iOS and macOS plugin implementations that were still using Pigeon 10/11 to the latest version (22). This picks up some minor improvements to serialization, as well as newer dependencies that can avoid resolver issues in flutter/flutter tests (see linked issue). Most of this PR is auto-generated via the repo tool's update-dependency command; only minor manual updates were required (mostly to test code). Fixes https://github.com/flutter/flutter/issues/1598031 年前
[url_launcher] Add Swift Package Manager support (#6677) Adds SPM support for both iOS and macOS. Also opportunistically updates the unit tests for macOS to match the changes made in https://github.com/flutter/packages/pull/4959 since I noticed that they were failing when running locally. This will prevent issues when we update CI in the future. Fixes https://github.com/flutter/flutter/issues/1469162 年前
[various] Update iOS/macOS Pigeon versions (#8226) Updates iOS and macOS plugin implementations that were still using Pigeon 10/11 to the latest version (22). This picks up some minor improvements to serialization, as well as newer dependencies that can avoid resolver issues in flutter/flutter tests (see linked issue). Most of this PR is auto-generated via the repo tool's update-dependency command; only minor manual updates were required (mostly to test code). Fixes https://github.com/flutter/flutter/issues/1598031 年前
Standardize Copyrights: Chromium->Flutter (#2996) In all copyright messages (and in the Xcode project organization name) standardize on "The Flutter Authors", adding "The Chromium Authors" to the Flutter AUTHORS list. This reduces inconsistency in the copyright lines in this repository, moving closer to a single consistent copyright+license (as in flutter/engine and flutter/flutter) Updates the validation script to no longer accept "The Chromium Authors" or "the Chromium project authors" in first-party code.5 年前
Update repo for 3.32 stable (#9311) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.32 stable release (except the first one, as the stable roller has already landed).1 年前
Standardize copyright year (#3737) Standardizes all first-party copyrights on a single year, as is done in flutter/flutter and flutter/engine. All code now uses 2013, which is the earliest year that was in any existing copyright notice. The script checks now enforce the exact format of first-party licenses and copyrights. Fixes flutter/flutter#784485 年前
[various] Update flutter.dev links to more reliable destinations (#6963) Contributes to https://github.com/flutter/website/issues/10363 by updating to the latest links and updating some links to use new /to/ links that can be updated as needed.1 年前
Update repo for 3.32 stable (#9311) Does all of the steps from https://github.com/flutter/flutter/blob/master/docs/ecosystem/release/Updating-Packages-repo-for-a-stable-release.md for the 3.32 stable release (except the first one, as the stable roller has already landed).1 年前
README.md

url_launcher_macos

The macos implementation of url_launcher.

Usage

This package is endorsed, which means you can simply use url_launcher 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.