mirror of https://github.com/pulumi/pulumi.git
cf28becb04
11605: Add jsonStringify to nodejs sdk r=Frassle a=Frassle <!--- Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation. --> # Description <!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. --> This isn't _quite_ right, because you could possibly end up with an output value being passed to stringify still via a custom replacer or toJson method, and we don't handle that. But I don't think we _can_ handle that as we'd need async in sync to do it. ## Checklist <!--- Please provide details if the checkbox below is to be left unchecked. --> - [x] I have added tests that prove my fix is effective or that my feature works <!--- User-facing changes require a CHANGELOG entry. --> - [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Service, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> - [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. --> Co-authored-by: Fraser Waters <fraser@pulumi.com> |
||
|---|---|---|
| .. | ||
| automation | ||
| mockpackage | ||
| runtime | ||
| sxs_ts_test | ||
| config.spec.ts | ||
| constants.ts | ||
| init.spec.ts | ||
| iterable.spec.ts | ||
| options.spec.ts | ||
| output.spec.ts | ||
| provider.spec.ts | ||
| resource.spec.ts | ||
| unwrap.spec.ts | ||
| util.ts | ||