aws-cdk-go-v2: default values not present in documentation

[a-h]

Describe the bug

In the TypeScript CDK, default values are displayed during LSP autocomplete:

Here, you can see the @default field is printed, showing that the default value is 128MB.

In the Go CDK, these default values are not printed, so it's not clear what the value would be if you didn't populate the field.

Expected Behavior

Expected the default values to be displayed in a similar format to the TypeScript variant.

Current Behavior

There are no default values displayed by the LSP.

Reproduction Steps

Create any CDK construct in Go, and trigger autocomplete on an optional field in the construct params struct. You will see that no @default value is displayed.

Possible Solution

The Go language server (gopls) uses the code comments to choose what to display to the user, but there are no default values printed in the Go code. Updating the code generation to include the @default section from the TypeScript code would include the default values in the Go LSP output.

	// The amount of memory, in MB, that is allocated to your Lambda function.
	//
	// Lambda uses this value to proportionally allocate the amount of CPU
	// power. For more information, see Resource Model in the AWS Lambda
	// Developer Guide.
	// Experimental.
	MemorySize *float64 `field:"optional" json:"memorySize" yaml:"memorySize"`

Additional Information/Context

No response

CDK CLI Version

2.54.0 (build 9f41881)

Framework Version

No response

Node.js Version

v16.14.2

OS

MacOS

Language

Go

Language Version

1.19 - but it's not relevant

Other information

No response

[peterwoodworth]

Thanks for reporting this! I'm going to translate it to the JSII repo where we handle the code conversion. Let's see what they say 🙂

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.