magus v0.3.0 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
2 min read

markdown

The markdown spell lints and formats Markdown. markdownlint enforces style, and prettier checks formatting; the rw charm turns the check into an in-place rewrite.

Runtime name: markdown (source spells/markdown/)

Version probe: none

Passing arguments to ops

Every op is invoked as markdown["<op>"](ctx, opts?). The first argument is the target's context, which is what carries the execution environment; the optional options map shapes the command itself:

Key Type Description Source
args [str] Extra arguments appended to the resolved command. Omit it and a bare markdown["<op>"]() forwards magus run <target> -- <extra> to the tool automatically; pass it to set the arguments explicitly, which replaces that passthrough. source
stdin str Data written to the command's standard input. source

Working directory and environment are NOT options: they ride the context, as markdown["<op>"](ctx.withCwd("sub")) and markdown["<op>"](ctx.withEnv({"CGO_ENABLED": "0"})). Only the context reaches the cache key, so an option-table cwd or env would change what the tool did while the key said otherwise - passing either as an option is an error.

Charms (the :charm suffix, e.g. magus run test:rw) are orthogonal: they patch the base argv, while these options add to it. See Charms.

markdownlint

Command: markdownlint **/*.md **/*.mdx

Example

// markdownlint enforces Markdown style across the docs.
import "magus";
import "magus/spell/markdown";

magus\project({ "spells": [markdown] });

export fun lint(ctx: magus\Context, args: [str]) > void {
    markdown["markdownlint"](ctx);
}

prettier

Command: prettier --check --no-error-on-unmatched-pattern **/*.md **/*.mdx

rw

Replaces --check with --write.

JSON Patch
[
  {
    "op": "replace",
    "path": "/0",
    "value": "--write"
  }
]

Example

// prettier checks Markdown formatting; the rw charm (magus run format:rw) rewrites in place.
import "magus";
import "magus/spell/markdown";

magus\project({ "spells": [markdown] });

export fun format(ctx: magus\Context, args: [str]) > void {
    markdown["prettier"](ctx);
}

typos

Command: typos --format brief

rw

Appends -w.

JSON Patch
[
  {
    "op": "add",
    "path": "/-",
    "value": "-w"
  }
]
auto-generatedmarkdownspelldocsprettierlinttools
Last updated (a103255f)
Earlier changes on this page (2)

Full history ↗ · Blame source ↗

Glossary

Project

A directory magus recognizes as a unit of work (it has a magusfile); the unit of caching, scheduling, and dependency tracking. See workspace.

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. See targets.

Spell

A language/runtime adapter (e.g. go, md) that maps generic targets onto a toolchain's real commands. See spells.

Charm

An execution modifier attached with : (lint:rw) that changes how a target runs, not which one; the built-in rw flips a check-only target to mutate in place, and ci always strips it. See charms.

Ward

A coded diagnostic that inspects a resolved op and nudges or blocks an anti-pattern before it runs. See wards.

Buzz

The language magusfiles are written in (the .buzz engine). See engines.

Cache

The content-addressed store magus consults before running a target, so unchanged work is skipped. See cache.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs - magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Conventions

Placeholders

Angle brackets mark a value you replace with your own - never type the brackets:

magus run <target>
magus completion <shell>    # e.g. bash, zsh, fish

<target>, <path>, <shell>, <name> and the like are stand-ins, not literal text.