Skip to content

[plugins] ☂️ Swift migration for 1P plugins #119015

@hellohuanlin

Description

@hellohuanlin

Motivation

Here is just a few benefits of doing so:

  • Null safety baked into the language
  • Many new features in Swift like tuples and structs
  • More and more system APIs only support Swift
  • More and more iOS developers/contributors only know Swift (or prefer Swift)

For more details, please refer to Swift migration design doc

Instruction

  1. IMPORTANT: Read the Swift migration section of the wiki

  2. Pick a plugin that you are interested in:

Note:

  • The above list is ordered by plugin size.
  • path_provider and shared_preferences is already done by reusing existing macOS implementation

Metadata

Metadata

Assignees

No one assigned

    Labels

    P3Issues that are less important to the Flutter projectpackageflutter/packages repository. See also p: labels.platform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtriaged-iosTriaged by iOS platform team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions