Update dependency apple/swift-argument-parser to v1 #27
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
from: "0.5.0"
->from: "1.2.2"
Release Notes
apple/swift-argument-parser
v1.2.2
Compare Source
Fixes
.allUnrecognized
parsing strategy no longer consumebuilt-in flags like
--help
and--version
. ([#550])names couldn't be parsed. ([#548])
synchronous
ParsableCommand.main()
static method to be run on anAsyncParsableCommand
type. ([#547])v1.2.1
Compare Source
Changes
Swift Package Index.
Fixes
exit(_:)
no longer causes infinite recursion on the WASI platform. ([#520])fish
now provide completions after anon-hyphen-prefixed argument has been provided. ([#535])
ExpressibleByArgument
types has been improved.([#522])
.postTerminator
arguments now includes the requiredterminator (
--
). ([#542])The 1.2.1 release includes contributions from [Chamepp], [kkk669], [mtj0928],
[natecook1000], [rauhul], [rickrizzo], [TiagoMaiaL], and [yim-lee]. Thank you!
v1.2.0
Compare Source
Additions
You can now provide a title in an
@OptionGroup
declaration. Titled optiongroups are listed separately in the help screen under that title as a
heading. ([#492])
Two new parsing strategies have been added for
@Argument
array properties:.allUnrecognized
captures all unrecognized inputs after parsing knownflags, options, and arguments.
.postTerminator
collects any inputs that follow the--
terminator.See the
ArgumentArrayParsingStrategy
documentation formore. ([#496])
Default values are now supported for
@Argument
or@Option
properties withoptional type, allowing you to initialize those properties with
nil
.Providing a non-
nil
default value results in a warning, since optionalproperties with non-
nil
defaults don't need to be declared as optionals.([#477], [#480])
Changes
.unconditionalRemaining
array parsing strategy has been deprecated andrenamed to
.captureForPassthrough
, to better fit its semantic behavior andintended usage. See the
ArgumentArrayParsingStrategy
documentation for more. ([#496])
Fixes
init(from:)
decoding initializers are now correctly diagnosed byArgumentParser's validators. ([#487])
@Flag
propertieswith inversions or
EnumerableFlag
types. ([#486])corrected to not show raw Swift values. Instead, the help display uses the
type's customized
defaultValueDescription
andallValues
implementations.([#494])
but different argument names no longer collide. ([#495])
generate-manual
plugin name is improved when used from within Xcode.([#505])
The 1.2.0 release includes contributions from [allevato], [clayellis],
[compnerd], [d-ronnqvist], [natecook1000], [randomeizer], and [rauhul].
Thank you!
v1.1.4
Compare Source
Changes
The generate-manual plugin now defaults to creating single page manuals. The
--single-page
flag has been replaced with--multi-page
to restore theprevious default functionality. ([#472])
Migration: Update scripts that invoked generate-manual without
--single-page
to include--multi-page
and update scripts that invokedgenerate-manual with
--single-page
to omit the flag.The "experimental" prefix from the generate-manual plugin has been removed.
([#475])
Migration: Update scripts to invoke the generate manual plugin via
swift package generate-manual
instead ofswift package plugin experimental-generate-manual
.Fixes
plugin visible to clients. ([#456])
--authors
arguments are now correctly passed tothe underlying generation tool. ([#471])
names and do not include value names for flags. ([#473])
--help
and--version
are now correctly marked asoptional fixing some generated content which indicated the flags are always
required. ([#474])
ExpressibleByArgument
andRawRepresentable
byString
. Help menus willnow display valid default values for such types. ([#476])
The 1.1.4 release includes contributions from [ian-twilightcoder],
[MarcoEidinger], and [rauhul]. Thank you!
v1.1.3
Compare Source
Additions
ArgumentParser
now includes a SwiftPM plugin for generatingman
pages.Explore the functionality and configuration by running
swift package plugin experimental-generate-manual --help
from your packageroot. ([#332])
Fixes
CaseIterable
type, the error messagenow includes a list of valid inputs. ([#445])
AsyncParsableCommand
is incorrectly placedunder a non-
async
root command. ([#436])The 1.1.3 release includes contributions from [keith], [KeithBird],
[konomae], [LucianoPAlmeida], and [rauhul]. Thank you!
v1.1.2
Compare Source
Changes
ArgumentParserToolInfo
.([#424])
Fixes
--key
)without any values, the error message now correctly describes the
problem. ([#435])
The 1.1.2 release includes contributions from [compnerd] and [KeithBird].
Thank you!
v1.1.1
Compare Source
Fixes
types and protocols with
async
members. This was a source-breakingchange in 1.1.0. ([#427])
v1.1.0
Compare Source
Additions
run()
method now supportsasync
/await
when the commandconforms to
AsyncParsableCommand
. ([#404])and option groups, and a new extended help screen accessible via
--help-hidden
. ([#366], [#390], and [#405 through #413][1.1.0])command. ([#400])
Changes
ArgumentParser
now requires Swift 5.5.Fixes
when over the length limit. ([#416])
@Option
initializer now has its parameters in the correct order; theincorrect initializer is deprecated. ([#391])
.unconditionalRemaining
argumentarrays.
The 1.1.0 release includes contributions from [keith], [MartinP7r], [McNight],
[natecook1000], [rauhul], and [zkiraly]. Thank you!
v1.0.3
Compare Source
Changes
When a user provides an incorrect value for an option, an
ArgumentParser
-based program now includes the valid values when possible.Fixes
zsh
custom completions for command names that includea dash.
fish
.ArgumentParser
for WebAssembly usingSwiftWasm toolchains.
--experimental-dump-help
with commands that providenon-parsed values.
.unconditionalRemaining
parsing strategy unexpectedly miss arguments,extending the change in [#333] to subcommands. ([#397])
@Option
initializer's parameters, deprecating theold version. ([#391])
The 1.0.3 release includes contributions from [atierian], [CraigSiemens],
[dduan], [floam], [KS1019], [McNight], [mdznr], [natecook1000], [rauhul], and
[yonihemi]. Thank you!
v1.0.2
Compare Source
Fixes
The 1.0.2 release includes a contribution from [jakepetroules]. Thank you!
v1.0.1
Compare Source
Fixes
The 1.0.1 release includes a contribution from [imxieyi]. Thank you!
v1.0.0
Compare Source
The 1.0 release marks an important milestone —
ArgumentParser
is now source stable!Changes
ArgumentParser
now provides a DocC documentation catalog, so youcan view rendered articles and symbol documentation directly within
Xcode.
Fixes
are declared using the
.upToNextOption
parsing strategy.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.