# gogoprotobuf Extensions
Here is an [example.proto](https://github.com/gogo/protobuf/blob/master/test/example/example.proto) which uses most of the gogoprotobuf code generation plugins.
Please also look at the example [Makefile](https://github.com/gogo/protobuf/blob/master/test/example/Makefile) which shows how to specify the `descriptor.proto` and `gogo.proto` in your proto_path
The documentation at [http://godoc.org/github.com/gogo/protobuf/gogoproto](http://godoc.org/github.com/gogo/protobuf/gogoproto) describes the extensions made to goprotobuf in more detail.
Also see [http://godoc.org/github.com/gogo/protobuf/plugin/](http://godoc.org/github.com/gogo/protobuf/plugin/) for documentation of each of the extensions which have their own plugins.
# Fast Marshalling and Unmarshalling
Generating a `Marshal`, `MarshalTo`, `Size` and `Unmarshal` method for a struct results in faster marshalling and unmarshalling than when using reflect.
See [BenchComparison](https://github.com/gogo/protobuf/blob/master/bench.md) for a comparison between reflect and generated code used for marshalling and unmarshalling.
Name | Option | Type | Description | Default |
nullable | Field | bool | if false, a field is generated without a pointer (see warning below). | true |
embed | Field | bool | if true, the field is generated as an embedded field. | false |
customtype | Field | string | It works with the Marshal and Unmarshal methods, to allow you to have your own types in your struct, but marshal to bytes. For example, custom.Uuid or custom.Fixed128 | goprotobuf type |
customname (beta) | Field | string | Changes the generated fieldname. This is especially useful when generated methods conflict with fieldnames. | goprotobuf field name |
casttype (beta) | Field | string | Changes the generated field type. It assumes that this type is castable to the original goprotobuf field type. It currently does not support maps, structs or enums. | goprotobuf field type |
castkey (beta) | Field | string | Changes the generated fieldtype for a map key. All generated code assumes that this type is castable to the protocol buffer field type. Only supported on maps. | goprotobuf field type |
castvalue (beta) | Field | string | Changes the generated fieldtype for a map value. All generated code assumes that this type is castable to the protocol buffer field type. Only supported on maps. | goprotobuf field type |
`Warning about nullable: according to the Protocol Buffer specification, you should be able to tell whether a field is set or unset. With the option nullable=false this feature is lost, since your non-nullable fields will always be set.`
`Warning about customtype: It is your responsibility to test all cases of your marshaling, unmarshaling and size methods implemented for your custom type.`
# Goprotobuf Compatibility
Gogoprotobuf is compatible with Goprotobuf, because it is compatible with protocol buffers (see the section on tests below).
Gogoprotobuf generates the same code as goprotobuf if no extensions are used.
The enumprefix, getters and stringer extensions can be used to remove some of the unnecessary code generated by goprotobuf.
Name | Option | Type | Description | Default |
gogoproto_import | File | bool | if false, the generated code imports github.com/golang/protobuf/proto instead of github.com/gogo/protobuf/proto. | true |
goproto_enum_prefix | Enum | bool | if false, generates the enum constant names without the messagetype prefix | true |
goproto_getters | Message | bool | if false, the message is generated without get methods, this is useful when you would rather want to use face | true |
goproto_stringer | Message | bool | if false, the message is generated without the default string method, this is useful for rather using stringer | true |
goproto_enum_stringer (experimental) | Enum | bool | if false, the enum is generated without the default string method, this is useful for rather using enum_stringer | true |
goproto_extensions_map (beta) | Message | bool | if false, the extensions field is generated as type []byte instead of type map[int32]proto.Extension | true |
goproto_unrecognized (beta) | Message | bool | if false, XXX_unrecognized field is not generated. This is useful to reduce GC pressure at the cost of losing information about unrecognized fields. | true |
# Less Typing
The Protocol Buffer language is very parseable and extra code can be easily generated for structures.
Helper methods, functions and interfaces can be generated by triggering certain extensions like gostring.
Name | Option | Type | Description | Default |
gostring | Message | bool | if true, a `GoString` method is generated. This returns a string representing valid go code to reproduce the current state of the struct. | false |
onlyone (deprecated) | Message | bool | if true, all fields must be nullable and only one of the fields may be set, like a union. Two methods are generated: `GetValue() interface{}` and `SetValue(v interface{}) (set bool)`. These provide easier interaction with a union. | false |
equal | Message | bool | if true, an Equal method is generated | false |
verbose_equal | Message | bool | if true, a verbose equal method is generated for the message. This returns an error which describes the exact element which is not equal to the exact element in the other struct. | false |
stringer | Message | bool | if true, a String method is generated for the message. | false |
face | Message | bool | if true, a function will be generated which can convert a structure which satisfies an interface (face) to the specified structure. This interface contains getters for each of the fields in the struct. The specified struct is also generated with the getters. This allows it to satisfy its own face. | false |
description (beta) | Message | bool | if true, a Description method is generated for the message. | false |
populate | Message | bool | if true, a `NewPopulated` function is generated. This is necessary for generated tests. | false |
enum_stringer (experimental) | Enum | bool | if true, a String method is generated for an Enum | false |
#Peace of Mind
Test and Benchmark generation is done with the following extensions: