Come up with a better name for Wasp's TS config

[sodic]

First, we called it TS SDK, which was confusing (and conflicting with our other SDK, which users import from).

Then we called it TS config, which is confusing because it conflicts with tsconfig.json.

We should come up with a good name for it.

[Martinsos]

• Wasp TS DSL
• Wasp TS Schema -> blah, no
• Wasp TS Definition

We can also try to imagine we have Python alternative in the future, so it should also work for that. So

• Wasp Python DSL
• Wasp Python Definition

It seems to me like DSL is the best but I wish I could think of something nicer.

[infomiho]

When I think about it, it's a Wasp Config file in the end. The language seems like a implementation details.

So it could be:

• Wasp Config in Typescript
• Wasp Config in Python
• Wasp Config in our DSL

Pulumi calls it project file and Encore doesn't really call it anything, just says, there is a encore.app file 😂

[Martinsos]

Ok there is away to go about it also! However "Wasp Config in Typescript" is a bit clunky, you will want to call it somehow shorter, and there is no way to do that. Also config sounds a bit overly simplistic hm. We will have multiple files soon, modules and what not. I am not saying this might not be the best name though, I am just pointing out cons.

But another idea that I only now remembered -> We have AppSpec, and Wasp itself is Web App SPecification -> so what about "Specification"?

Typescript (Wasp) Spec(ification)
DSL (Wasp) Spec
Python (Wasp) Spec

At the end that is the whole idea of Waps -> you capture specification in this higher-level language, and you do implementation in JS and React and so on. So, it is specification. Yeah hm can we even name it anything else.

[sodic]

Wasp Spec vs TypeScript Spec sound great!