Romain Marcadier
Romain Marcadier
I've actually been thinking about this *a lot* recently, and I sure am very favorable to this idea. I'm not sure when we'll have time to work on this however......
Counter-proposition... How about allowing a TSDoc-annotation that allows the developer to force a particular declaration to be interpreted as a compatible semantic structure: ```ts /** * This interface would normally...
Ack - it's actually present in the Prerequisites sections of the user guides (https://aws.github.io/jsii/user-guides/lib-author/), however there is no reason why it shouldn't also be in the language support matrix (in...
I have this idea where I'd like to allow folks to *own* their `tsconfig.json` and basically only have `jsii` enforce the configuration remains within certain boundaries (to ensure correct inter-operability)....
> An example of this can be seen with the discord-bot-cdk-construct project, where [Discord's APIs expects allowed_mentions (ie: camel case)](https://github.com/GEMISIS/discord-bot-cdk-construct/blob/main/src/types.ts?rgh-link-date=2022-04-01T07%3A44%3A36Z#L94). However, because there is no way to disable JSII8002, it...
See: https://docs.microsoft.com/dotnet/standard/serialization/system-text-json-how-to
Hey! Thanks for this feature request. If C# 9.0 allows covariant return types, then we could be able to alleviate the restriction, however the minimum supported target is C# 9.0+,...
@tomas-mazak this is correct!
> Is there a recommended pattern for getting around this issue? Not really. C# very strictly enforces Liskov's substitutability... so we kind of have to abide, otherwise we cannot represent...