Namespace all types by their API version

[boourns]

🔴 FOR DISCUSSION 🔴

I'm exploring an approach for the WAM2 API/SDK to support WAMs built with older versions of the API/SDK.

The general idea is that, when an older WAM is loaded, WamEnv will need to wrap the older WAM with a shim object that implements backwards compatibility, so that the rest of the system can treat the old WAM as if it were built with the current SDK version.

One requirement to do this easily will be to know the typescript definitions for older WAM SDKs. So the idea here is, each API version defines its types inside a Vx.y.z namespace, and then the API exposes the "current" versions.

I'm interested in your thoughts, alternative approaches, whether you agree this is a problem we need to solve, ...

Some things I'm uncertain about:

• can we move the export const definitions out of types.d.ts and into the versioned namespace.
• should versions be wrapped in a module, or a namespace?

Next steps, other problems that would need to be solved as well:

• On load WAMs made with an older SDK version should be wrapped with an interop layer to upgrade them to the newer SDK version
• Similarly, the WamEnv that is exposed to a WAM built with an older SDK would have to implement the older WamEnv API. This will likely require refactoring the WamEnv interface that a WAM sees, so that we can easily shim this layer to what the older WAM would expect. For example WAMs should not be able to get direct references from one to another, or else we'd need to have shims all OVER the place 😬

[boourns]

I think I found a less intrusive way to implement a shim for WAMs built with older SDKs, so closing this