GGitHub[tool] Use swift-format from Xcode (#9460 )

111ceb70创建于 2025年6月26日历史提交

文件	最后提交记录	最后更新时间
example	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).	11 个月前
ios	[tool] Use `swift-format` from Xcode (#9460) As of Xcode 16, `swift-format` is part of the Xcode distribution. Since CI now uses Xcode 16, we can just always use that version. This: - Removes the `swift-format-path` logic. - Removes the check for `swift-format` being available - Defaults Swift formatting to true only on macOS - Removes the `swift-format` CIPD package from .ci.yaml - Updates Pigeon in packages using Swift Pigeon generation to pick up a fix for a lint issue picked up by the latest version of `swift-format` (which was already fixed in Pigeon). Fixes https://github.com/flutter/flutter/issues/153803 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	10 个月前
lib	[tool] Use `swift-format` from Xcode (#9460) As of Xcode 16, `swift-format` is part of the Xcode distribution. Since CI now uses Xcode 16, we can just always use that version. This: - Removes the `swift-format-path` logic. - Removes the check for `swift-format` being available - Defaults Swift formatting to true only on macOS - Removes the `swift-format` CIPD package from .ci.yaml - Updates Pigeon in packages using Swift Pigeon generation to pick up a fix for a lint issue picked up by the latest version of `swift-format` (which was already fixed in Pigeon). Fixes https://github.com/flutter/flutter/issues/153803 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	10 个月前
pigeons	[url_launcher] When not fully loaded, clicking close causes the callback to not be triggered correctly. (#8582) When SFSafariViewController is loading a webpage, if the close button is clicked during the loading process, it can prevent the callback from being triggered correctly. List which issues are fixed by this PR. You must list at least one issue. - Fixes https://github.com/flutter/flutter/issues/161790 - Fixes https://github.com/flutter/flutter/issues/47271	1 年前
test	[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/159803	1 年前
AUTHORS	[url_launcher] Federate mobile implementations (#4515) Fully federates the plugin by moving the existing mobile implementations to their own packages, per planned repo structure. Temporarily marks `url_launcher` 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 https://github.com/flutter/flutter/issues/68498	4 年前
CHANGELOG.md	[tool] Use `swift-format` from Xcode (#9460) As of Xcode 16, `swift-format` is part of the Xcode distribution. Since CI now uses Xcode 16, we can just always use that version. This: - Removes the `swift-format-path` logic. - Removes the check for `swift-format` being available - Defaults Swift formatting to true only on macOS - Removes the `swift-format` CIPD package from .ci.yaml - Updates Pigeon in packages using Swift Pigeon generation to pick up a fix for a lint issue picked up by the latest version of `swift-format` (which was already fixed in Pigeon). Fixes https://github.com/flutter/flutter/issues/153803 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	10 个月前
LICENSE	[url_launcher] Federate mobile implementations (#4515) Fully federates the plugin by moving the existing mobile implementations to their own packages, per planned repo structure. Temporarily marks `url_launcher` 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 https://github.com/flutter/flutter/issues/68498	4 年前
README.md	[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 年前
pubspec.yaml	[tool] Use `swift-format` from Xcode (#9460) As of Xcode 16, `swift-format` is part of the Xcode distribution. Since CI now uses Xcode 16, we can just always use that version. This: - Removes the `swift-format-path` logic. - Removes the check for `swift-format` being available - Defaults Swift formatting to true only on macOS - Removes the `swift-format` CIPD package from .ci.yaml - Updates Pigeon in packages using Swift Pigeon generation to pick up a fix for a lint issue picked up by the latest version of `swift-format` (which was already fixed in Pigeon). Fixes https://github.com/flutter/flutter/issues/153803 ## Pre-Review Checklist [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.	10 个月前

url_launcher_ios

The iOS 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.