public static class VixenCommandThe vixen command line.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
Every command takes its writers rather than reaching for Console, so the tests drive the same parser a person does and read what it said. A CLI whose behaviour can only be checked by running a process is one whose behaviour is not checked.
A verb that parses and then apologises is worse than one that is not there, because a build script can only discover the second kind. That rule is why new, run and build were absent until doc 17's shipping story gave them something to wrap, and it is why live up, live down and live upgrade --content still are. It is also why remesh has no --bake: docs/plan/41 § D16's example line has one and the bake is R5's, so the flag arrives with the maps it would write.
Methods (1)
public static RootCommand Create(TextWriter? output = null, TextWriter? error = null)Builds the command line.
Used by (10)
- DoctorBehaviorsTestsVixen.Cli.Tests
- DoctorSystemsTestsVixen.Cli.Tests
- FrameCommandTestsVixen.Cli.Tests
- GeometryCommandTestsVixen.Cli.Tests
- LiveCommandTestsVixen.Cli.Tests
- MeshMapCommandTestsVixen.Cli.Tests
- ProjectPluginTestsVixen.Cli.Tests
- TextureCommandTestsVixen.Cli.Tests
- TraceCommandTestsVixen.Cli.Tests
- VixenCommandTestsVixen.Cli.Tests