Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lists members should be generated as values by default #128

Closed
jasdel opened this issue Aug 5, 2020 · 0 comments · Fixed by #232
Closed

Lists members should be generated as values by default #128

jasdel opened this issue Aug 5, 2020 · 0 comments · Fixed by #232

Comments

@jasdel
Copy link
Contributor

jasdel commented Aug 5, 2020

Member's of List shapes should not be generated as pointer values by default. The members of lists should be generated as values.

This changes how the SDK generator and serializers handle list/set shapes. During deserialization the SDK should substitute the type's zero value for null values, and during serialization send the value of the list member.

@jasdel jasdel changed the title Lists should be generated as values by default Lists members should be generated as values by default Aug 5, 2020
@jasdel jasdel added this to the v1.0 Release Candidate milestone Nov 13, 2020
jasdel added a commit that referenced this issue Nov 15, 2020
…#232)

Adds a new KnowedgeIndex implementation GoPointableIndex this index declares when a shape should be a pointer or value type in Go code. Updates the SDK's code generation so that all non-sparse list and maps are rendered with value members instead of pointers. This null-ability applies to number and boolean members to that are not explicitly decorated as boxed.

Fixes #128
Fixes #127
Fixes #149
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant