The package manifest
What is still open for the .nyxp manifest: typed settings, editor support and version ranges
The manifest is described in Packages and projects, with its errors in Errors, and a script’s directives, which say what a manifest would, in Files and projects. How it is read is on The nanyx command. This page keeps what is still open. It is part of the packaging workstream.
What’s not built
- Settings typed by a record type. A host declares the settings it takes in its own manifest, with their
defaults, and a program’s
settingsfor it are checked against them (The HTTP host). The plan is for a linter or host to export its settings as a record type instead, and for the entry’ssettingsto be checked against it with the ordinary type checker, so a misspelt key is an ordinary type error, with a span, naming the package. It needs the package’s module compiled first, which happens anyway before it runs. For linters it waits on linters being packages (#1343); until then a linter’ssettingshold onlyrules, which the compiler checks itself. - Hover and completion in the manifest. The extension highlights and formats a
.nyxp, and the language server checks it as you type, but there is no hover or completion in it; completion on asettingsfield is to list the package’s settings. - The formatter as a configured tool. Its settings are the
formatterfield, which the formatter reads itself. It could become a configured tool like a linter later.
Open questions
- Version ranges. A string (
"^2.1", or"2.1"meaning caret, as Packages and projects says), or tags (#caret("2.1"),#exact("0.28.0"))? Versions are strings: a linter’s or host’sversionis an exact version string,"0.28.0".