Skip to content

Commit e4b2583

Browse files
committed
Replace swift migrate with swift package migrate
1 parent 84c2fca commit e4b2583

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

proposals/NNNN-adoption-tooling-for-swift-features.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Migration tooling for Swift features
22

3-
* Proposal: [SE-NNNN](NNNN-filename.md)
3+
* Proposal: [SE-NNNN](NNNN-migratable-features.md)
44
* Authors: [Anthony Latsis](https://github.com/AnthonyLatsis), [Pavel Yaskevich](https://github.com/xedin)
55
* Review Manager: TBD
66
* Status: **Awaiting implementation**
@@ -160,16 +160,16 @@ belong to a diagnostic group named after the feature.
160160
The names of diagnostic groups can be displayed alongside diagnostic messages
161161
using `-print-diagnostic-groups` and used to associate messages with features.
162162

163-
### `swift migrate` command
163+
### `swift package migrate` command
164164

165-
To enable seemless migration experience for Swift packages, I'd like to propose a new Swift Package Manager command - `swift migrate` to complement the Swift compiler-side changes.
165+
To enable seemless migration experience for Swift packages, I'd like to propose a new Swift Package Manager command - `swift package migrate` to complement the Swift compiler-side changes.
166166

167167
The command would accept one or more features that have migration mode enabled and optionally a set of targets to migrate, if no targets are specified the whole package is going to be migrated to use new features.
168168

169169
#### Interface
170170

171171
```
172-
USAGE: swift migrate [<options>] --to-feature <to-feature> ...
172+
USAGE: swift package migrate [<options>] --to-feature <to-feature> ...
173173
174174
OPTIONS:
175175
--targets <targets> The targets to migrate to specified set of features or a new language mode.
@@ -181,7 +181,7 @@ OPTIONS:
181181
#### Use case
182182

183183
```
184-
swift migrate --targets MyTarget,MyTest --to-feature ExistentialAny
184+
swift package migrate --targets MyTarget,MyTest --to-feature ExistentialAny
185185
```
186186

187187
This command would attempt to build `MyTarget` and `MyTest` targets with `ExistentialAny:migrate` feature flag, apply any fix-its associated with
@@ -211,7 +211,7 @@ enable the feature(s) if both of the previous actions are successful:
211211
In the "whole package" mode, every target is going to be updated to include
212212
new feature flag(s). This is supported by the same functionality as `swift package add-setting` command.
213213

214-
If it's, for some reason, impossible to add the setting the diagnostic message would suggest what to add and where i.e. `...; please add '.enableUpcomingFeature("ExistentialAny")' to `MyTarget` target manually`.
214+
If it's, for some reason, impossible to add the setting the diagnostic message would suggest what to add and where i.e. `...; please add 'ExistentialAny' feature to `MyTarget` target manually`.
215215

216216
#### Impact on Interface
217217

@@ -345,7 +345,7 @@ The next candidates in line per discussions are ***adopt***, ***audit***,
345345
To illustrate, this mode could appropriately suggest switching from `any P`
346346
to `some P` for `ExistentialAny`.
347347

348-
### `swift migrate` vs. `swift package migrate`
348+
### `swift package migrate` vs. `swift migrate`
349349

350350
Rather than have migrate as a subcommand (ie. `swift package migrate`), another option is add another top level command, ie. `swift migrate`.
351351

0 commit comments

Comments
 (0)