init

import SwiftProtobuf

Support library for Swift code generated by protoc-gen-swift.

struct Google_Protobuf_MethodOptions

static let _protobuf_nameMap: _NameMap

static let protoMessageName: String

var _protobuf_extensionFieldValues: ExtensionFieldValueSet

var deprecated: Bool { get set }

Is this method deprecated? Depending on the target platform, this can emit Deprecated annotations for the method, or it will be completely ignored; in the very least, this is a formalization for deprecating methods.

var features: Google_Protobuf_FeatureSet { get set }

Any features defined in the specific edition. WARNING: This field should only be used by protobuf plugins or special cases like the proto compiler. Other uses are discouraged and developers should rely on the protoreflect APIs for their client language.

var hasDeprecated: Bool { get }

Returns true if deprecated has been explicitly set.

var hasFeatures: Bool { get }

Returns true if features has been explicitly set.

var hasIdempotencyLevel: Bool { get }

Returns true if idempotencyLevel has been explicitly set.

var idempotencyLevel: Google_Protobuf_MethodOptions.IdempotencyLevel { get set }

var isInitialized: Bool { get }

var uninterpretedOption: [Google_Protobuf_UninterpretedOption]

The parser stores options it doesn’t recognize here. See above.

var unknownFields: UnknownStorage

static func == (lhs: Google_Protobuf_MethodOptions, rhs: Google_Protobuf_MethodOptions) -> Bool

mutating func clearDeprecated()

Clears the value of deprecated. Subsequent reads from it will return its default value.

mutating func clearFeatures()

Clears the value of features. Subsequent reads from it will return its default value.

mutating func clearIdempotencyLevel()

Clears the value of idempotencyLevel. Subsequent reads from it will return its default value.

mutating func decodeMessage<D>(decoder: inout D) throws where D : Decoder

func traverse<V>(visitor: inout V) throws where V : Visitor

enum IdempotencyLevel

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.