Create high level typescript API alongside auraescript but in its own repo

[bpmooch]

I'd like to split auraescript into its own repo. Auraescript has the potential to be a novel way to interact with an aurae cluster. It is, however, in more of a state of experimentation than auraed. Splitting auraescript out and the required release management work to do so will benefit auraescript and auraed, getting us to a mature gRPC API more quickly than the current setup

[dmah42]

by "auraescript" do you mean "a typescript API"? i wonder if we continue to support auraescript as a generated low-level typescript API but in addition we create a separate high level abstraction API in typescript as a separate repo.

much as we've done with ae.

[bpmooch]

I mean a high level typescript api. I have no opinion in terms of naming. Could you expand a little bit on how you see the software arch for auraed -> auraescript -> high level api?

[dmah42]

there are two options for a typescript API i think:

1. auraed -> auto-generated auraescript -> hand-written typescript high-level API that offers an abstracted logic
2. auraed -> hand-written typescript high-level API that offers an abstracted logic

the former means that out-of-the-box we get an API that anyone can use which is aligned with the auraed version. but some people might want a more abstract API than we can auto-generate.

[bpmooch]

by "auraescript" do you mean "a typescript API"? i wonder if we continue to support auraescript as a generated low-level typescript API but in addition we create a separate high level abstraction API in typescript as a separate repo.

much as we've done with ae.

I didn't fully understand what you meant by this!! yes this is the way