Acknowledged — this is a pre-existing bug in the resource string CommandLineOptionIsReserved which uses {0} for both placeholders: Option '--{0}' is reserved and cannot be used by providers: '{0}'. The {1} placeholder was never wired up. Fixing the resource string would change the error message (a behavior change) and requires regenerating xlf localization files — that's out of scope for this performance PR. Our code correctly collects the provider names via reservedOptionToProviderNames so that when the resource string is eventually fixed, it will just work. I'd suggest filing a separate issue to fix the resource string.
Originally posted by @Evangelink in #5655 (comment)
Acknowledged — this is a pre-existing bug in the resource string
CommandLineOptionIsReservedwhich uses{0}for both placeholders:Option '--{0}' is reserved and cannot be used by providers: '{0}'. The{1}placeholder was never wired up. Fixing the resource string would change the error message (a behavior change) and requires regenerating xlf localization files — that's out of scope for this performance PR. Our code correctly collects the provider names viareservedOptionToProviderNamesso that when the resource string is eventually fixed, it will just work. I'd suggest filing a separate issue to fix the resource string.Originally posted by @Evangelink in #5655 (comment)