You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When SwiftPM is run with an invalid command, it could be caused by a typo or because the user does not remember the precise command. By having SwiftPM detect those cases and suggest the correct command, SwiftPM would be more friendly to use.
This feature could be implemented by modifying ArgumentParser to use the new Ordered Collection Diffing API in Swift 5.1 to compare the invalid command to the available commands and suggest on close matches.
Here's an example what it could look like:
$swiftbuild --packagepath ../patherror: unknownoption --packagepath; use --helptolistavailableoptionsDidyoumean --package-path?
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: b19bc070247bf50f8ed031dab4bb7a15
Issue Description:
When SwiftPM is run with an invalid command, it could be caused by a typo or because the user does not remember the precise command. By having SwiftPM detect those cases and suggest the correct command, SwiftPM would be more friendly to use.
This feature could be implemented by modifying
ArgumentParser
to use the new Ordered Collection Diffing API in Swift 5.1 to compare the invalid command to the available commands and suggest on close matches.Here's an example what it could look like:
The text was updated successfully, but these errors were encountered: