Context
From PR #5535 discussion — the func new redesign needs an option for the template output directory (analogous to dotnet new --output), but --output / -o is already used across v5 commands to control rendering format (plain/json).
Currently --output means "format" on:
func newfunc startfunc setup
This forces the template output directory to use --path, which is ambiguous.
Proposal
Rename the format option from --output to --format across all commands, then use --output / -o for directory targeting on func new (and potentially func init), matching dotnet new --output conventions.
Why now is a good time
--output as format is a v5-only convention — v4 doesn't use it- v5 is still in preview, so breaking changes are expected
- Aligning with
dotnet new --output reduces learning curve
Scope
Needs a CLI-wide audit of --output usage and a coordinated rename across all affected commands.
Context
From PR #5535 discussion — the
func newredesign needs an option for the template output directory (analogous todotnet new --output), but--output/-ois already used across v5 commands to control rendering format (plain/json).Currently
--outputmeans "format" on:func newfunc startfunc setupThis forces the template output directory to use
--path, which is ambiguous.Proposal
Rename the format option from
--outputto--formatacross all commands, then use--output/-ofor directory targeting onfunc new(and potentiallyfunc init), matchingdotnet new --outputconventions.Why now is a good time
--outputas format is a v5-only convention — v4 doesn't use itdotnet new --outputreduces learning curveScope
Needs a CLI-wide audit of
--outputusage and a coordinated rename across all affected commands.