jsoneditor VS dhall-lang

This error is harmless. However, your configuration file is malformed. What u/mart1d4 said is right that the custom settings are for custom games mode (not hard). Start with the default config. You can use: https://jsoneditoronline.org/ to check your file formatting.

It really depends on the device and what software it comes with natively. You should be able to edit it in whatever notes/text-based editor comes on your phone. There are also websites you can upload it to and edit it through a browser like https://jsoneditoronline.org/ or https://jsonformatter.org/json-editor

I just checked, there are online JSON editors [1][2] you can edit that file in, just remove the "var data = " in the front and the ";" at the end. (need to add that back at the end so it works again)

Open the file with notepad and paste the text into an online editor like https://jsoneditoronline.org/ then just find the `"LuaScript": ...` field and substitute the whole line(s) for: `"LuaScript": "",`

Sorry for the formatting. PipeDream seems to prefer to work with it in this way. To view it better visit: JSON Editor

Save your .ady file and open it here: https://jsoneditoronline.org/

I took a quick look at that turquoise guide, seems ok if you’re able to follow it. I was going to suggest googling a JSON editor/formatter like this, you would open the file with that or paste the text and it will convert it to the tree structure that will make it a little easier to navigate. JSON is just a text file, and you can open it with notepad, but I wouldn’t recommend trying to search it that way. Better to use some kind of editor to get it into the tree structure.

Fail to see how this is any different than Dhall (https://dhall-lang.org/) other than it produces plists too.

Kubernetes config is a decent example. I had ChatGPT generate a representative silly example -- the content doesn't matter so much as the structure:

https://gist.github.com/cstrahan/528b00cd5c3a22e3d8f057bb1a7...

Now consider 100s (if not 1000s) of such files.

I haven't given Pkl an in depth look yet, but I can say that the Industry Standard™ of "simple YAML" + string substitution (with delicate, error prone indentation -- since YAML is indentation sensitive) is easily beat by any of:

- https://jsonnet.org/

- https://nickel-lang.org/

- https://nixos.org/manual/nix/stable/language/index.html

- https://dhall-lang.org/

- (insert many more here, probably including Pkl)

There are underpowered languages / tools, that can only solve a problem for which they are intended poorly. But not all limited tools are like that.

Say, eBPF is prominently not Turing-complete, which allows to guarantee that a eBPF program terminates, and even how soon. Still eBPF is hugely useful in its area.

Or, say, regular expressions are limited to regular languages; in particular, they famously [1] cannot process recursive structures, like trees. Still tools like grep / ag / rg are mightily useful.

Yes, I agree that YAML is underpowered for proper k8s configuration! But it's also too powerful for its own good in other aspects [2]. I wish Google used Dhall [3] or their own purely functional config language (FCL? I already forgot the name) instead of YAML; sadly, they did not.

[1]: https://stackoverflow.com/a/1732454/223424

[2]: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-fr...

[3]: https://dhall-lang.org/

Dhall: Dhall is a programmable configuration language that combines features like JSON, functions, types, and import capabilities. Its style leans towards functional programming, so if you're familiar with functional-style languages such as Haskell, you might find Dhall to be quite intuitive.

I've been thinking along these lines but more 'strongly validated' than statically typed in the sense that you'd be better off being able to load the entire config and then produce a list of problems (and should be able to offer good editor support if done correctly).

Though https://dhall-lang.org/ demonstrates that you can statically type quite a lot of configuration to great advantage, which appears to be programmatically embeddable in multiple languages per https://docs.dhall-lang.org/howtos/How-to-integrate-Dhall.ht...

> Where practical is in the sense of an engineer (or in their terms, a CS practitioner),

Configuration processing. E.g. I'd like my yamls to be decidable, though I'd settle for guaranteed to halt[1].

[1] https://dhall-lang.org/

Maybe you'd like jsonnet: https://jsonnet.org/

I find it particularly useful for configurations that often have repeated boilerplate, like ansible playbooks or deploying a bunch of "similar-but" services to kubernetes (with https://tanka.dev).

Dhall is also quite interesting, with some tradeoffs: https://dhall-lang.org/

A few years ago I did a small comparison by re-implementing one of my simpler ansible playbooks: https://github.com/retzkek/ansible-dhall-jsonnet

And to checkout Dhall: https://dhall-lang.org/