Leslie Fung

Hi @janainascal, can you provide a bit more context on with regard to "import API Configuration directly API package". Do you have a more complete example that might help me...

Hi @renatoathaydes, sorry for the delayed response. Yup its exactly what you assumed, Spot currently doesn't expect recursive types.

> Any motivation on why it was initially not permitted would be beneficial! This was considered, but was not a priority use case for us. Ultimately we deemed TypeScript's indexed...

> recursive -> 🔴 The type parser would need to be modified to pass around some sort "type parse stack" structure to keep track of types currently being parsed as...

> Absolutely, I am curious though, what about scenarios which could enable an open-ended pair of single level JSONs? Do you mean to allow index signatures only where no sibling...

I'm thinking a simpler way to constrain the usage could be TypeScript's `Record` type. The parser would only need to constrain the first type argument to `string` - disallowing `number`...

> inline type works great when the Generic object is small, but when its big and frequently referenced, the cost of expanding it every where goes up very quickly. The...

> The type parser would need to be modified to pass around some sort "type parse stack" structure to keep track of types currently being parsed as it traverses the...

I'm leaning towards allowing an optional option to point to a `tsconfig` file. @ccakes Spot has not been tested with external type definitions. I'll take a look at how we...

Hi @jankuca, sorry for the delay, I've been away the past week 🙏. As you've suggested this is a limitation of the OpenAPI 3.0 specification. Whilst your solution solves for...