Jo Wood

Error message reporting invalid column truncates column name

1

If reference is made to a non-existent column, an error message is (as expected) reported. However it appears to truncate the name of the misnamed column, missing off the first...

Cannot sort faceted boxplots when extent is "min-max"

2

Boxplots can be nicely sorted by some aggregation function with faceting: ```javascript { "$schema": "https://vega.github.io/schema/vega-lite/v3.json", "config": { "view": {"stroke": ""}, "header": {"labelAngle": 0}, "facet": {"spacing": 0} }, "data": { "values":...

Color scale interpolation with expression generates fatal 'Cannot read property 'signalRef' of undefined' error

1

Setting a [color interpolation type via an expression](https://vega.github.io/vega-lite/docs/scale.html#continuous-scales) generates a _Cannot read property 'signalRef' of undefined_ error. For example, ```json { "$schema": "https://vega.github.io/schema/vega-lite/v5.json", "data": {"values": [{ "val": 1},{"val": 2},{"val": 3}]},...

Use of local files in interactive mode in VSCode

5

We can reference data sources in three ways: 1. Inline directly encoded with `dataFromColumns` etc 2. Referencing a local file with `dataFromUrl`, e.g. `dataFromUrl "myFile.csv"` 3. Referencing an (usually remote)...

Thanks to @nickysinclair for bringing this to my attention: In VSCode, but not Atom, the following Litvis document will not preview the image when stored locally. Examples here use triple-hat...

syntax highlighting in VSCode requires space between elm and open brace

3

Code block headers expressed as `elm{l}` and `elm {l}` (note the space in the second example) both work. In Atom syntax highlighting is applied to the block of code correctly,...

Repeated shadow function definition across documents doesn't trigger error message

3

If you create a document containing the following two functions ````markdown ```elm {l} myFunction : String myFunction = let repeatedName = "Hello" in repeatedName ``` ```elm {r} repeatedName : String...

Some function types generate parsing warning in markdown mode

11

For the record, we still need to implement markdown output for a wider range of types. Currently some types can generate parsing warnings. For example ```` ```elm {m} myFunction :...

Suppose we have a function defined in a document: ### parent.md ```` ```elm{l=hidden} myFunction : String myFunction = "Hello from parent" ``` ```` And if a child document that follows...

Currently narrative schemas can only be linked a 'root' document. If a document `follows` another, it cannot directly link to a schema in its own frontmatter. A consequence of this...