Go to file
Jeff Carr f363c23176 add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
.gitignore test works 2024-11-29 10:20:06 -06:00
LICENSE add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
Makefile minor mv code 2024-12-04 15:35:27 -06:00
README add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
addMutex.go duh. TRUNC files 2024-12-11 13:50:38 -06:00
apple.proto add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
argv.go lots of fixes in gitpb 2024-12-17 06:34:27 -06:00
control add control file 2024-12-18 03:02:44 -06:00
header.go add version and DO NOT EDIT to header 2024-12-16 00:18:30 -06:00
main.go fix path. add notes to help install protoc 2024-12-18 02:54:14 -06:00
marshal.go duh. TRUNC files 2024-12-11 13:50:38 -06:00
parseProtoFile.go go-clone --build 2024-12-01 22:21:09 -06:00
protoc.go fix path. add notes to help install protoc 2024-12-18 02:54:14 -06:00
sort.go start thinking about redoing the sort function 2024-12-27 14:43:21 -06:00
sortnew.go start thinking about redoing the sort function 2024-12-27 14:43:21 -06:00

README

This app will autogenerate protobuf Sort() and Marshal() functions

It was designed to work on .proto files designed with a standard
way that utilizes this method:

apple.proto should have

message Apples {
	string uuid
	string version
	repeaded Apple Apples
}

message Apple {
	<whatever you want here>
}

This "scheme" as it were will be familar to others as a common way to pluralize data formats.
In general, this is turning out to be a good way to handle protocol buffers for me so far.

There are several things that can be put in the protobuf file to trigger what files are made.

See the examples for how to do this.