Current Status

At the moment, we’re ditching all of this for static links, since the type is known and none of this is useful. Arguably it makes sense for discoverability reasons, but I don’t like the overhead that implies, and scrapping that for now lets us move forward.

We can definitely have wrapper types of links as long as they all agree to a standard structure, probably with an href property, that the Toolkit can understand.

Motivation

Requirements

• It needs to fully support generics, especially to be interoperable with List.

❓

• How do we handle generics? Do we need structured tuples?
• What about thin wrappers around resource classes? This is important for collections and for Linking!

Draft

.veneto

type Link<T> = { 
	href: string, 
	type: string[], 
}

❓ Implementation

How do we handle codegen when the links are accessed dynamically?

A big question here is the mapping between serialized text and data types in the implementation. This has to be something that we can codegen around.