status-go/protocol/protobuf/service.go

package protobuf

import (
	"github.com/golang/protobuf/proto"
)

//go:generate protoc --go_out=. ./chat_message.proto ./application_metadata_message.proto ./membership_update_message.proto ./command.proto ./contact.proto ./pairing.proto ./push_notifications.proto ./emoji_reaction.proto ./enums.proto ./group_chat_invitation.proto ./chat_identity.proto

func Unmarshal(payload []byte) (*ApplicationMetadataMessage, error) {
	var message ApplicationMetadataMessage
	err := proto.Unmarshal(payload, &message)
	if err != nil {
		return nil, err
	}

	return &message, nil
}
Move to protobuf for Message type (#1706) * Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage` * Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text. * Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not. * Change the various retrieveX method to a single one: `RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is: `Chats`: -> The chats updated by receiving the message `Messages`: -> The messages retrieved (already matched to a chat) `Contacts`: -> The contacts updated by the messages `RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away. 2019-12-05 17:25:34 +01:00			`package protobuf`
Add datasync, v1messages & disable discovery topic options Adds support for datasync, V1Messages and disabling the discovery topic. This is a backward compatible change as long as they are not toggled on (they are not by default). 2019-07-26 09:17:29 +02:00
			`import (`
			`"github.com/golang/protobuf/proto"`
			`)`

make generate 2020-10-02 15:43:43 +01:00			`//go:generate protoc --go_out=. ./chat_message.proto ./application_metadata_message.proto ./membership_update_message.proto ./command.proto ./contact.proto ./pairing.proto ./push_notifications.proto ./emoji_reaction.proto ./enums.proto ./group_chat_invitation.proto ./chat_identity.proto`
Add datasync, v1messages & disable discovery topic options Adds support for datasync, V1Messages and disabling the discovery topic. This is a backward compatible change as long as they are not toggled on (they are not by default). 2019-07-26 09:17:29 +02:00
Move to protobuf for Message type (#1706) * Use a single Message type `v1/message.go` and `message.go` are the same now, and they embed `protobuf.ChatMessage` * Use `SendChatMessage` for sending chat messages, this is basically the old `Send` but a bit more flexible so we can send different message types (stickers,commands), and not just text. * Remove dedup from services/shhext. Because now we process in status-protocol, dedup makes less sense, as those messages are going to be processed anyway, so removing for now, we can re-evaluate if bringing it to status-go or not. * Change the various retrieveX method to a single one: `RetrieveAll` will be processing those messages that it can process (Currently only `Message`), and return the rest in `RawMessages` (still transit). The format for the response is: `Chats`: -> The chats updated by receiving the message `Messages`: -> The messages retrieved (already matched to a chat) `Contacts`: -> The contacts updated by the messages `RawMessages` -> Anything else that can't be parsed, eventually as we move everything to status-protocol-go this will go away. 2019-12-05 17:25:34 +01:00			`func Unmarshal(payload []byte) (*ApplicationMetadataMessage, error) {`
			`var message ApplicationMetadataMessage`
Add datasync, v1messages & disable discovery topic options Adds support for datasync, V1Messages and disabling the discovery topic. This is a backward compatible change as long as they are not toggled on (they are not by default). 2019-07-26 09:17:29 +02:00			`err := proto.Unmarshal(payload, &message)`
			`if err != nil {`
			`return nil, err`
			`}`

			`return &message, nil`
			`}`