anmolitor / elm-protoc-types / Proto.Google.Protobuf.SourceCodeInfo

This file was automatically generated by

To run it, add a dependency via elm install on elm-protocol-buffers version latest or higher.


type alias Location =
Proto.Google.Protobuf.Internals_.Proto__Google__Protobuf__SourceCodeInfo__Location

Fields

path

Identifies which part of the FileDescriptorProto was defined at this location.

Each element is a field number or an index. They form a path from the root FileDescriptorProto to the place where the definition occurs. For example, this path: [ 4, 3, 2, 7, 1 ] refers to: file.message_type(3) // 4, 3 .field(7) // 2, 7 .name() // 1 This is because FileDescriptorProto.message_type has field number 4: repeated DescriptorProto message_type = 4; and DescriptorProto.field has field number 2: repeated FieldDescriptorProto field = 2; and FieldDescriptorProto.name has field number 1: optional string name = 1;

Thus, the above path gives the location of a field name. If we removed the last element: [ 4, 3, 2, 7 ] this path refers to the whole field declaration (from the beginning of the label to the terminating semicolon).

span

Always has exactly three or four elements: start line, start column, end line (optional, otherwise assumed same as start line), end column. These are packed into a single field for efficiency. Note that line and column numbers are zero-based -- typically you will want to add 1 to each before displaying to a user.

leadingComments

If this SourceCodeInfo represents a complete declaration, these are any comments appearing before and after the declaration which appear to be attached to the declaration.

A series of line comments appearing on consecutive lines, with no other tokens appearing on those lines, will be treated as a single comment.

leading_detached_comments will keep paragraphs of comments that appear before (but not connected to) the current element. Each paragraph, separated by empty lines, will be one comment element in the repeated field.

Only the comment content is provided; comment markers (e.g. //) are stripped out. For block comments, leading whitespace and an asterisk will be stripped from the beginning of each line other than the first. Newlines are included in the output.

Examples:

optional int32 foo = 1; // Comment attached to foo. // Comment attached to bar. optional int32 bar = 2;

optional string baz = 3; // Comment attached to baz. // Another line attached to baz.

// Comment attached to moo. // // Another line attached to moo. optional double moo = 4;

// Detached comment for corge. This is not leading or trailing comments // to moo or corge because there are blank lines separating it from // both.

// Detached comment for corge paragraph 2.

optional string corge = 5; /* Block comment attached * to corge. Leading asterisks * will be removed. / / Block comment attached to * grault. */ optional int32 grault = 6;

// ignored detached comments.

decodeLocation : Protobuf.Decode.Decoder Location

Declares how to decode a Location from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.

defaultLocation : Location

Default for Location. Should only be used for 'required' decoders as an initial value.

encodeLocation : Location -> Protobuf.Encode.Encoder

Declares how to encode a Location to Bytes. To actually perform the conversion to Bytes, you need to use Protobuf.Encode.encode from eriktim/elm-protocol-buffers.

fieldNumbersLocation : { path : Basics.Int, span : Basics.Int, leadingComments : Basics.Int, trailingComments : Basics.Int, leadingDetachedComments : Basics.Int }

The field numbers for the fields of Location. This is mostly useful for internals, like documentation generation.

jsonDecodeLocation : Json.Decode.Decoder Location

Declares how to decode a Location from Bytes. To actually perform the conversion from Bytes, you need to use Protobuf.Decode.decode from eriktim/elm-protocol-buffers.

jsonEncodeLocation : Location -> Json.Encode.Value

Encode a Location to JSON. Uses the canonical encoding described here: https://protobuf.dev/programming-guides/proto3/#json