Cue is a little different I think. It doesn't attempt to make writing configs less tedious through the use of functions.

It is more about schemas and reliably merging documents as far as I can tell. But weirdly given its focus on schemas I couldn't find any way for a document to link to a schema in-band!

It makes writing configs less tedious using templates.

Not really sure what you mean by "documents" though.

Some config formats like Yaml or Jsonl support multiple "documents" per file

I mean multiple files.

> But weirdly given its focus on schemas I couldn't find any way for a document to link to a schema in-band!

In cue there's no real distinction between "schemas" and "documents". If you say:

   value: string
   value: "abc"

then cue "unifies" the definitions for `value`, sees that "abc" is a string, and therefore `value` is valid.

Yes I know, but there's no in-band way to say "this file conforms to the schema in this other file" like you can with XML or JSON schemas.

For Cue you would probably just want to #include a file... but as far as I know you can't do that.

That makes it far less useful for IDEs, linters and so on.

I don't think there's any reason they couldn't add that feature. Just a bit odd that they haven't already.

And https://nickel-lang.org/ too.

relevant: https://github.com/tweag/nickel#comparison-with-other-config...

FWIW, "YAML Typing = None" is for sure wrong, that's what the `!!map` annotations (https://yaml.org/spec/1.1/#tag/syntax) are for, and a very common RCE vector for dynamic languages since they can cause execution when the parser instantiates the types