How do i ser/de a response

[quinn]

	messages, err := graphClient.Users().ByUserId("***").Messages().
		Get(context.Background(), &users.ItemMessagesRequestBuilderGetRequestConfiguration{
			QueryParameters: &users.ItemMessagesRequestBuilderGetQueryParameters{
				Top:     ptr(int32(10)),
				Orderby: []string{"receivedDateTime desc"},
			},
		})
	if err != nil {
		return fmt.Errorf("failed to get messages: %v", err)
	}
	bytes, err := json.Marshal(messages)
	if err != nil {
		return fmt.Errorf("failed to marshal message: %v", err)
	}
	fmt.Printf("%s\n", bytes)

returns:

{}

How can I get the "raw" response body, and unmarshal it into the correct type later? When I ctrl+click into it, its just indecipherable code-generated interfaces.

[baywet]

Hi @quinn
Thank you for using the SDK and for reaching out.

The objects are already deserialized for you, that's one of the advantages of using the SDK.

messages.GetValue()[0].GetSubject()

should give you the subject of the first message

Let us know if you have any additional comments or questions.

[quinn]

I don’t have additional questions, but I would like my original question answered:

1. how do I serialize the object returned by the sdk
2. With that data, how do I serialize it back into the object returned by the sdk

[baywet]

// serialization
// https://github.com/microsoft/kiota-serialization-json-go/blob/a93555fbc1a377dc7e746fd5ba9f3a7cdb444600/json_serialization_writer.go#L34
writer := json.NewJsonSerializationWriter()
err = writer.WriteObjectValue("", messages)
bytes, err := writer.GetSerializedContent()

// deserialization
// https://github.com/microsoft/kiota-serialization-json-go/blob/a93555fbc1a377dc7e746fd5ba9f3a7cdb444600/json_parse_node.go#L28
parseNode, err := json.NewJsonParseNode(bytes)
deserialized, err := parseNode.GetObjectValue(models.CreateMessageCollectionResponseFromDiscriminatorValue)

[quinn]

Thanks, @baywet

I get that you’re building a code generator to support as many languages as possible, but it would be nice if the golang code behaved in a more idiomatic way, for example returning concrete types instead of interfaces. It would also be nice if the objects could be serialized in the conventional way, since the underlying api is just returning json, it should be feasible to return structs that have the standard struct tags.

I’m guessing your code generator assumes a more OOP environment, it seems like you have some sort of storage layer which is accessed thru getter methods, which doesn’t map well to go conventions. I assume you have your reasons.

Thanks for your help, your example code is what I’m looking for 👍

[baywet]

The main reason for the interface + getter approach is because of inheritance. If an operation describes returning a collection of directory objects, but really returns a bunch of user, group, application (all of which derive from directory objects), you need to be able to "downcast" (type assert) to the derived type so you can access the specialized properties. And unfortunately in Go that's only possible through interfaces.