View Source Protobuf behaviour (protobuf v0.17.0)
protoc should always be used to generate code instead of writing the code by hand.
Usage
By use'ing this module, macros defined in Protobuf.DSL will be injected. Most of these
macros are equal to definition in .proto schemas.
defmodule Foo do
use Protobuf, syntax: :proto3
field :a, 1, type: :int32
field :b, 2, type: :string
endYour Protobuf message (module) is just a normal Elixir struct. The default values in the struct match the correct ones for the Protobuf schema definition. You can construct new messages by hand:
foo = %Foo{a: 1}
Protobuf.encode(foo)
#=> <<...>>Except functions in "Callbacks", some other functions may be defined:
- Extension functions when your Protobuf message use extensions. See
Protobuf.Extensionfor details.put_extension(struct, extension_mod, field, value)get_extension(struct, extension_mod, field, default \ nil)
Options
These are the options that you can pass to use Protobuf:
:syntax- The syntax of the schema. Can be:proto2or:proto3. Defaults to:proto2.:enum- A boolean that tells whether this message is an enum. Defaults tofalse.:map- A boolean that tells whether this message is a map. Defaults tofalse.
Summary
Types
Describes whether a field is present in a Protobuf message.
Represents a field that existed in a decoded message, but didn't exist in the used protobuf definition.
Internal wire type
Callbacks
Decodes a Protobuf binary into a struct.
Encodes the given struct into to a Protobuf binary.
Returns the fully qualified name of the descriptor's target.
Returns the name of the source .proto file that defined this message, or nil.
Returns nil or a transformer module that implements the Protobuf.TransformModule
behaviour.
Functions
Decodes the given binary data interpreting it as the Protobuf message module.
Encodes the given Protobuf struct into a binary.
Encodes the given Protobuf struct into iodata.
Returns whether a field is present, not present, or maybe present.
Returns the unknown fields that were decoded but were not understood from the schema.
Checks if the given value is a Protobuf message struct.
Loads extensions modules.
Types
@type field_presence() :: :present | :not_present | :maybe
Describes whether a field is present in a Protobuf message.
:maybe means that the field uses implicit presence and its value is equal to
the generated default, so the struct cannot tell whether it was explicitly set.
Represents a field that existed in a decoded message, but didn't exist in the used protobuf definition.
See get_unknown_fields/1 for more information.
@type wire_type() :: 0..5
Internal wire type
Callbacks
Decodes a Protobuf binary into a struct.
Errors may be raised if there's something wrong in the binary.
This callback does not take decoding options. To pass options (such as :max_nesting_depth),
use Protobuf.decode/3 instead.
Encodes the given struct into to a Protobuf binary.
Errors may be raised if there's something wrong in the struct.
If you want to encode to iodata instead of to a binary, use encode_to_iodata/1.
@callback full_name() :: String.t()
Returns the fully qualified name of the descriptor's target.
@callback proto_source() :: String.t() | nil
Returns the name of the source .proto file that defined this message, or nil.
This is the file name as known to protoc (for example "my/test/test.proto"),
taken from the FileDescriptorProto. It is only populated when code is generated
with the gen_proto_source=true plugin option; otherwise it returns nil.
@callback transform_module() :: module() | nil
Returns nil or a transformer module that implements the Protobuf.TransformModule
behaviour.
This function is overridable in your module.
Functions
@spec decode(binary(), message, keyword()) :: %{ :__struct__ => message, optional(atom()) => any() } when message: module()
Decodes the given binary data interpreting it as the Protobuf message module.
This function raises an error if anything goes wrong with decoding.
Options
:max_nesting_depth- the maximum number of nested embedded messages allowed before decoding raises aProtobuf.DecodeError. Decoding a deeply-nested or self-referential message can otherwise drive unbounded recursion and exhaust memory and CPU. Defaults to100, matching the reference Protobuf implementations. Available since v0.16.1.
Examples
Protobuf.decode(<<...>>, MyMessage)
#=> %MyMessage{...}
Protobuf.decode(<<"bad data">>, MyMessage)
#=> ** (Protobuf.DecodeError) ...
Encodes the given Protobuf struct into a binary.
If you want to encode to iodata instead, see encode_to_iodata/1.
Examples
Protobuf.encode(%MyMessage{...})
#=> <<...>>
Encodes the given Protobuf struct into iodata.
Examples
Protobuf.encode_to_iodata(%MyMessage{...})
#=> [...]
@spec field_presence(message :: struct(), field :: atom()) :: field_presence()
Returns whether a field is present, not present, or maybe present.
:present and :not_present mean that a field is explicitly present or not
present, respectively.
Some fields use implicit presence. For example, an empty repeated field and a
non-optional proto3 scalar set to its default value are indistinguishable from
their generated defaults. In these cases, this function returns :maybe.
For more information about field presence tracking rules, refer to the official Field Presence docs.
Examples
# Non-optional proto3 field:
Protobuf.field_presence(%MyMessage{foo: 42}, :foo)
#=> :present
Protobuf.field_presence(%MyMessage{foo: 0}, :foo)
#=> :maybe
# Optional proto3 field:
Protobuf.field_presence(%MyMessage{bar: 42}, :bar)
#=> :present
Protobuf.field_presence(%MyMessage{bar: 0}, :bar)
#=> :present
Protobuf.field_presence(%MyMessage{}, :bar)
#=> :not_present
# Repeated field:
Protobuf.field_presence(%MyMessage{items: []}, :items)
#=> :maybe
Protobuf.field_presence(%MyMessage{items: [1]}, :items)
#=> :present
@spec get_unknown_fields(struct()) :: [unknown_field()]
Returns the unknown fields that were decoded but were not understood from the schema.
In Protobuf, you can decode a payload (for the same message) encoded with a different version of the schema for that message. This can result in, for example, the payload containing fields that cannot be decoded correctly because they're not present in the schema used for decoding. These fields are skipped, but in some cases you might wish to preserve them in order to re-encode them, log them, or other. A common case is having to do "round-trips" with messages: you decode a payload, update the resulting message somehow, and re-encode it for future use. In these cases, you would probably want to re-encode the unknown fields to maintain symmetry.
The returned value of this function is a list of {field_number, wire_type, field_value} tuples where
field_number is the number of the unknown field in the schema used for its encoding and
field_value is its value. The library does not make any assumptions on the value of the
field since it can't know for sure. This means that, for example, it can't properly decode
an integer as signed or unsigned. The only guarantee is that the unknown fields are re-encoded
correctly.
The reason why these fields need to be accessed through this function is that the way they are stored in the struct is private.
Examples
Imagine you have this Protobuf schema:
message User {
string email = 1;
}You encode this:
payload = Protobuf.encode(%User{email: "user@example.com"})
#=> <<...>>Now, you try to decode this payload using this schema instead:
message User {
string full_name = 2;
}In this case, this function will return the decoded unknown field:
message = User.decode(<<...>>)
Protobuf.get_unknown_fields(message)
#=> [{_field_number = 1, _wire_type = 3, "user@example.com"}]
Checks if the given value is a Protobuf message struct.
This guard checks for the __protobuf__: true marker that is automatically added
to all Protobuf message structs.
Examples
defmodule MyMessage do
use Protobuf, syntax: :proto3
field :name, 1, type: :string
end
message = %MyMessage{name: "test"}
iex> is_protobuf_message(message)
true
iex> is_protobuf_message(%{})
falseCan be used in guards:
def process_message(msg) when is_protobuf_message(msg) do
msg.name
end
@spec load_extensions() :: :ok
Loads extensions modules.
This function should be called in your application's Application.start/2 callback,
as seen in the example below, if you wish to use extensions.
Example
@impl Application
def start(_type, _args) do
Protobuf.load_extensions()
Supervisor.start_link([], strategy: :one_for_one)
end