Formerly andreasewering/elm-protoc-types. Search finds this package by either name.
This file was automatically generated by
protoc-gen-elm 3.3.4protoc 4.22.2google/protobuf/descriptor.protoTo run it, add a dependency via elm install on elm-protocol-buffers version latest or higher.
Declares how to decode a IdempotencyLevel from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.
Default for IdempotencyLevel. Should only be used for 'required' decoders as an initial value.
Declares how to encode a IdempotencyLevel to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.
The field numbers for the fields of IdempotencyLevel. This is mostly useful for internals, like documentation generation.
Convert the internal type Proto__Google__Protobuf__MethodOptions__IdempotencyLevel into a IdempotencyLevel.
Using two different types is necessary to avoid recursive module references while having readable constructor names.
Encode a IdempotencyLevel to JSON. Uses the canonical encoding described here: https://protobuf.dev/programming-guides/proto3/#json
Convert a IdempotencyLevel into its internal representation Proto__Google__Protobuf__MethodOptions__IdempotencyLevel.
Using two different types is necessary to avoid recursive module references while having readable constructor names.
Is this method side-effect-free (or safe in HTTP parlance), or idempotent, or neither? HTTP based RPC implementation may choose GET verb for safe methods, and PUT verb for idempotent methods instead of the default POST.