Justin Van Patten

I've opened https://github.com/pulumi/pulumi/issues/8701 to track considering doing this in the Node.js SDK codegen.

We should investigate whether using JSDoc `{@link}` would do what we want. (Need to see how this comes back from TypeDoc). https://jsdoc.app/tags-inline-link.html

Yep, I'll take a look and report back.

Editor support for `@see` and `{@link}` in JSDoc comment tags is on the roadmap for TypeScript 4.1. https://github.com/microsoft/TypeScript/issues/35524

I made some very minor improvements in #1690 to Python, but it could use a couple more hours cleaning up the styling across the board. Going to move this out...

Hi @bgdnlp, > The Python docs are hard to follow, at least for someone new to Pulumi. The styling on Typescript pages looks much better. We are planning some significant...

Thanks for opening the issue, @ripom, and sorry for the trouble! The primary issue is that the examples should be showing the use of the input classes (where the argument...

Thanks, for opening the issue, @aardbol. Totally agree this doesn't look right. Unfortunately, it's a consequence of https://github.com/pulumi/pulumi/issues/3151. We automatically map camelCase names to snake_case for Python dicts, but we...

This does look like a more involved fix is required. While I'd love to fix this, I think some of the other fixes we want to do this milestone have...

The [definition from the source](https://github.com/pulumi/pulumi-kubernetes/blob/be175ccf22a33e9724f2b259ff9390cd77504b09/sdk/nodejs/yaml/yaml.ts#L79): ```typescript transformations?: ((o: any, opts: pulumi.CustomResourceOptions) => void)[]; ``` The [docs](https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/kubernetes/yaml/#ConfigFileOpts-transformations): ```typescript transformations?: (o: any, opts: CustomResourceOptions) => void[]; ``` The docs are just missing...