Go to file
Jeff Carr 57f8f88ae9 simple example build test is correct for both mutex 2025-01-10 17:49:14 -06:00
example simple example build test is correct for both mutex 2025-01-10 17:49:14 -06:00
.gitignore example is working okay 2025-01-09 20:08:22 -06:00
LICENSE add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
Makefile simple example build test is correct for both mutex 2025-01-10 17:49:14 -06:00
README add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
addMutex.go make seperate find and sort files 2025-01-10 11:22:08 -06:00
argv.go hotfix 2025-01-10 04:37:54 -06:00
control add control file 2024-12-18 03:02:44 -06:00
file.proto make seperate find and sort files 2025-01-10 11:22:08 -06:00
header.go iterator top done? 2025-01-09 06:47:35 -06:00
main.go maybe a function I can use with patchsets.proto 2025-01-10 12:19:22 -06:00
marshal.go compiles again 2025-01-09 15:03:05 -06:00
protoParse.go make seperate find and sort files 2025-01-10 11:22:08 -06:00
protoc.go mutex's are being added to the protoc pb.go file 2025-01-09 05:49:23 -06:00
sort.go simple example build test is correct for both mutex 2025-01-10 17:49:14 -06:00
sortFunc.go simple example build test is correct for both mutex 2025-01-10 17:49:14 -06:00
sortNew.go simple example build test is correct for both mutex 2025-01-10 17:49:14 -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.