Skip to content

Conversation

@loic-sharma
Copy link
Member

@loic-sharma loic-sharma commented Nov 14, 2024

Overview

This splits the Swift Package Manager feature in two:

  1. SwiftPM feature: This builds plugins using SwiftPM (if the app supports it), and, uses the new app & plugin templates that support SwiftPM
  2. SwiftPM app migration feature: this updates an existing Flutter iOS or macOS app to support Swift Package Manager. This feature requires the SwiftPM feature - if SwiftPM is off, the app migration is also off.

For now, both features are off by default. We plan to turn on the first feature in the next stable release. The app migration feature will be stay off by default until we have higher confidence in the migration.

See this mini design doc: #151567 (comment)

Here's the PR that updates the SwiftPM docs: flutter/website#11495

Part of #151567

Pre-launch Checklist

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@github-actions github-actions bot added platform-ios iOS applications specifically tool Affects the "flutter" command-line tool. See also t: labels. a: desktop Running on desktop labels Nov 14, 2024
@github-actions github-actions bot removed the platform-ios iOS applications specifically label Nov 19, 2024
@loic-sharma loic-sharma force-pushed the spm_migration_flag branch 7 times, most recently from d5acab3 to 282b63a Compare November 21, 2024 22:40
@loic-sharma loic-sharma mentioned this pull request Nov 22, 2024
9 tasks
@loic-sharma loic-sharma force-pushed the spm_migration_flag branch 3 times, most recently from 739706c to e73825a Compare December 12, 2024 23:31
@loic-sharma loic-sharma marked this pull request as ready for review December 13, 2024 23:25
Copy link
Contributor

@andrewkolos andrewkolos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with nits. If you end up needing another review after monorepo/formatting merges, just let me know.

plistParser: FakePlistParser(),
features: TestFeatureFlags(),
features: TestFeatureFlags(
isSwiftPackageManagerMigrationEnabled: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we explicitly disable SPM here for the sake of clarity?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer to as well. However, that results in a warning that tells you not to provide an argument if the value is the default value. I'm not a huge fan of this warning 😦

Copy link
Member

@jmagman jmagman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM once testWith/WithoutContext is used in tests.

@loic-sharma loic-sharma force-pushed the spm_migration_flag branch 2 times, most recently from 9457216 to 0c7c5b1 Compare January 4, 2025 01:34
@loic-sharma loic-sharma added the autosubmit Merge PR when tree becomes green via auto submit App label Jan 7, 2025
@auto-submit auto-submit bot added this pull request to the merge queue Jan 7, 2025
Merged via the queue into flutter:master with commit e7a1b68 Jan 7, 2025
165 checks passed
@flutter-dashboard flutter-dashboard bot removed the autosubmit Merge PR when tree becomes green via auto submit App label Jan 7, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 7, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 8, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 8, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 8, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Jan 8, 2025
@loic-sharma
Copy link
Member Author

Reason for revert: This PR should be in the same release as #161275. However, #161275 had to be reverted and won't be relanded until after the release cutoff. Hence, I'm reverting this as well.

@loic-sharma loic-sharma added the revert Autorevert PR (with "Reason for revert:" comment) label Jan 8, 2025
@auto-submit
Copy link
Contributor

auto-submit bot commented Jan 8, 2025

Time to revert pull request flutter/flutter/158897 has elapsed.
You need to open the revert manually and process as a regular pull request.

@auto-submit auto-submit bot removed the revert Autorevert PR (with "Reason for revert:" comment) label Jan 8, 2025
loic-sharma added a commit to loic-sharma/flutter that referenced this pull request Jan 8, 2025
loic-sharma added a commit to loic-sharma/flutter that referenced this pull request Jan 8, 2025
github-merge-queue bot pushed a commit that referenced this pull request Jan 9, 2025
…58897)" (#161342)

This reverts #158897 (commit
e7a1b68) as it is intended to be in the
same release as #161275.

However, #161275 had to be
reverted and won't be relanded until after the release cutoff. Hence,
I'm reverting this as well.
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 12, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 13, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Feb 13, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 6, 2025
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a: desktop Running on desktop tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants