Rico Hermans

Yeah, I see where you're coming from. It's just this: we're building a class library that we recommend people to write extensions for using VSCode, and we intend to parse...

Would be very useful to me as well

@thespacedoctor I have a tiny fix that (completely unconfigurably) shows the total issue count on a branch: https://github.com/rix0rrr/jasper/pull/1 At some point I'd be happy to make this configurable and contribute...

I'm not sure this works if there are two stacks, and only one is deployed with a new version of the asset. In my mind, the other stack should still...

> Now that I think about it, versioning would only help if we were regularly re-uploading files. That's probably not the case? I thought you meant expiration for non-current versions....

I've been thinking about this as well. In my head, it was a graphical "construct builder" with copy/pasteable snippets on the right, rather than a downloadable project. No reason why...

The naive implementation of this in C# would look like (passing a union type as a struct parameter, which is very common because all L1s have that): ``` new CfnUserPool(...,...

We remove the hidden APIs from the `.d.ts` files. The one I don't have a solution for will be JavaScript users, but how will they know certain functions exist in...

> app.synth() which is stable returns cxapi.CloudAssembly which is experimental Yeah, that doesn't make sense, and I'm having a hard time thinking of models in which we can express this....

The simplest solution would seem to be generating `JSX.IntrinsicElements` declarations for all constructs and publishing those as a separate library, right? Then it's easy to add in `key` and `ref`...