Update the standard library names and add the `importbin` statement to
update the syntax highlighting to jsonnet v0.19.1.
The standard library names have been automatically generated with the
following command:
PROG='std.lines(["syn match Constant \"std.%s\"" % fn for fn in std.objectFieldsAll(std) if fn[0] >= "a" && fn[0] <= "z"])''
go run github.com/google/go-jsonnet/cmd/jsonnet@v0.19.1 --string - <<<"${PROG}"
This should make it easier to keep up-to-date with additions to the
standard library, as it was missing some rather old additions. Seems to
have been rather adhoc.
As part of this automation, the builtins and `std.jsonnet` have been
combined as there is no way to determine which names are builtin and
which come from `std.jsonnet`. Manually maintaining the distinction is
pointless busywork, and that fell behind anyway as a bunch of
`std.jsonnet` functions have been migrated to builtins for performance
reasons.
The automation script lists the names in the `std` object, ignoring all
names that do not start with a lower-case letter. This removes some
internal names that should not be added to the syntax highlighting.
The `importbin` statement was manually added.
so that a `|||` in the middle of a multiline string does not end the string
according to the syntax highlighter unless it actually ends it
according to the language.
From the jsonnet spec:
> Text block, beginning with `|||`, followed by optional
whitespace and a new-line. The next non-blank line must be prefixed
with some non-zero length whitespace *W*. The block ends at the first
subsequent line that does not begin with *W*, and it is an error if this
line does not contain some optional whitespace followed by `|||`.
Prior to this change, the syntax highlighter looked for any sequence `|||`
as the end-of-string marker. This causes problems in multiline strings that
contain this sequence (this mostly comes up when providing example usage).
Example:
```
{
help: |||
To use this foo, you should specify a description like so:
{
description: |||
Your description here.
|||,
}
|||,
...
}
```
In this example, the line `Your description here.` would be considered outside
any string, with the part before it and the part after it being considered
two distinct strings.
We make the syntax highlighter use the same rules as the spec by making the
start pattern match `|||` followed by any amount of whitespace, then any number
of newlines (blank lines), then an amount of whitespace (*W* in the spec).
It uses the `\z( \)` construct to make this a subgroup accessible to the end pattern.
The end pattern uses lookaround to say that the start of the line must not match
the *W* from the start token, while still being any amount of whitespace then `|||`.
* Update jsonnet.vim
Add missing standard libraries to syntax highlighting.
Add special syntax highlighting to python style string formatting inside of strings.
* Update jsonnet.vim
If the exists('*exepath') evaluates to false vim was returning this
error:
Error detected while processing function
<SNR>10_fmtAutosave..jsonnet#Format..jsonnet#CheckBinPath:
line 6:
E121: Undefined variable: binPath
Added documentation, a vim command, a user callable function and an
autocommand that gets executed at every save.
The defaults are hight configurable with options that are also
documented in this change.
