hypothetical question 1

[glacial parrot]

.

If we shipped a version of cloak that literally didn't have the extensions feature, would that version of cloak still need to load a cloak.yaml file?

[wispy canopy]

Not that I can think of, no

[glacial parrot]

what about the SDK config you mentioned: is that how we'll hook up eg. the new client-side codegen stuff @dusky bronze is working on?

[wispy canopy]

I think we can just re-use language native features for that (i.e. //go generate directives, npm scripts, etc.)

extensions are different because they are essentially dependencies, but as discussed a long time ago trying to use language native dependency managers for our use case is really hard

[dusky bronze]

Not required.

Code generation needs some information. Can be passed to the generate command instead (what the codegen POC is doing).

Putting that in the manifest is syntactic sugar so all options are consolidated into a single place rather than scattered around

e.g.

• for extensions, we need to know the language (to compile the extension)
• for codegen, we need to know the language (to generate stubs in the right language)

and so they both share the same information from cloak.yaml to avoid repetition. But not required.

Unless I'm forgetting something

But for instance in this morning's demo I had an empty cloak.yaml (not an extension and didn't need to import extensions)