jetify-com/tyson

🥊 TypeScript as a Configuration Language. TySON stands for TypeScript Object Notation

tyson's Issues

Feature Request - Terraform Provider

What

It seems like typically configuration languages come with a terraform provider which I think unlocks a lot of potential.

It'd be really cool to see the same for a project like this!

For Example

• https://registry.terraform.io/providers/awakesecurity/dhall/latest/docs
• https://registry.terraform.io/providers/poseidon/cue/latest/docs
• https://registry.terraform.io/providers/alxrem/jsonnet/latest/docs

Embeddable configuration types

I've been playing with TySON and I've been liking where this can go. I would like to be able to have my application ship a "config drive" or something in the form of an io.FS/embed.FS that's pre-baked with the type definitions. This would let me ship the types by default so I can write TySON configs like this:

import { Config } from "internal/config.ts";

export default {
  foo: "bar",
} satisfies Config;

What do you think about this? Shipping the types to editors would probably be a little bit hard, but I think it could be doable with some legwork.

First read - random thoughts

Hi,

I have just discovered this project

First of all, it's interesting

---

The first question that came to my mind was : what features are not supported but are supported by TypeScript ? Then i see that another issue is already open #3

---

I think JSONC (JSON with Comments) should be listed in the related work section

---

AFAIU, Tyson will be typed, which will transpile into JSON which is not typed, which will be parsed by a program which will be probably be typed

I think this is not optimal to lose the type in the stream

---

How will you synchronise the program's type with Tyson's type ?

---

I feel comfortable with jsonc + JSON Schema or Yaml + schema

Note of humour https://xkcd.com/927/

Continuation Lines

Can we have lines that span multiple lines? I notice your back-tick string allows newlines inside the quoted string, but how can you create values that are longer than a line in the editor?

Classically a line ending with a back-slash would allow line extension. JSON does not allow this and so a very long string spills off the right-hand-side of the editor.

Since TySon generates JSON, continuation lines would translate to very-long-strings.

What is the difference between this and using TypeScript?

I don't really understand which TypeScript features are not supported. Since functions and string interpolation are included, how is this different from TypeScript itself? Maybe it would be helpful to specify what is not included in TSON.

In other words, is a JS runtime needed to parse TSON?