Expand description
How a fix line or a next step is taken from an interface: speccoder
performs it, opens a view, runs the person’s own command, or it belongs
in the person’s shell. One parser (step_of) for every line speccoder
prints, so no interface copies a command speccoder can take itself.
Structs§
- Context
- What a line is about when it does not say: the result’s feature and task.
- Step
- A line with how it is taken.
Enums§
- How
- How an interface takes a line.
- View
- A read-only place an interface opens instead of running a command.
Constants§
- PR_
CONFIRM - The confirmation a pull request asks for (it leaves the machine).
- SUBCOMMANDS
- speccoder’s subcommands: a line that starts
speccoderand goes on with anything else is words (speccoder did not create …).
Functions§
- interactive
argvreads the keyboard — a sign-in’s prompt or device flow, an editor, a question — so it needs a terminal of the person’s own.- outside
- What
argvchanges outside the project when it is one of the few fixes that, by their nature, cannot run confined to it: those run outside the sandbox, and say so. Every other runs in it. - person
- The person’s own command a source built as argvs: shown as the line a
shell would read (
render), run exactly as given. - render
- Argvs as a shell reads them: a word with anything but plain characters
single-quoted;
&&between them. - signing
- Runs
fwithsignersigning every command step built meanwhile on this thread (itstoken): a host that runs commands signs only the steps speccoder itself builds, never JSON from elsewhere. - step_of
- How
lineis taken, withctxfilling what it leaves open. - steps
- Every line of
fix, as steps. - steps_
with - Every line of
fix, as steps; a line a source gave as argvs (typed, rendered to that line) is those argvs.
Type Aliases§
- Argvs
- Argvs run one after the other (
a && b).