Brandon Bloom

Pull requests welcome on this issue. Thanks.

Looks like some work in this direction landed in #125, but this is not working quite yet because of what seems to be a TypeScript shortcoming and/or bug. Here's a...

I think there are three separate issues wrapped up in here. 1) control over floating point printing. 2) extensible formatting of tagged-literals, similar to what is supported symbols. > .toFixed...

Hey @jleonard-r7, if I understand correctly, what you're asking for here is support for round-tripping of unreadable symbols (ie those with invalid syntax, but valid runtime representations). The round-tripping pair...

Did you ever find a workaround for this issue?

I stopped seeing this issue when I fixed an unrelated bug with my validation code. Not sure the details, was already 4 days ago.

Note: @kendru reported that this has some subtle bugs still.

I'm struggling with a similar problem with certificates now too. The idiom there seems to be to create a `aws:acm:CertificateValidation` resource, which waits for validation to complete the create operation....

I also wanted to use this library in a transport-agnostic way, so I extracted the marshaling/encoding bits to another package: https://github.com/deref/graphql-go/tree/d269e7a529c689bc6fbd40814615844d9a1e47ef#encoding Thanks to @dmitshur for his excellent work on this...

This is now supported in my transport-agnostic fork: https://github.com/deref/graphql-go The specific changes are here: https://github.com/deref/graphql-go/compare/c7885fdd0fbc0a4061a3d40e31a14a48b57d6726...e2b473959845be6782ba490d7372a82f3704bd4b