Go to file
Jeff Carr b0ceb9e1b4 rename 2025-01-09 06:09:09 -06:00
testfiles builds 2025-01-09 03:42:29 -06:00
.gitignore testfiles dir 2025-01-08 19:58:29 -06:00
LICENSE add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
Makefile mutex's are being added to the protoc pb.go file 2025-01-09 05:49:23 -06:00
README add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
addMutex.go verbage to inform someone that looks 2025-01-09 06:05:38 -06:00
argv.go make a protofile for the app itself 2025-01-08 19:45:48 -06:00
auto.proto mutex's are being added to the protoc pb.go file 2025-01-09 05:49:23 -06:00
control add control file 2024-12-18 03:02:44 -06:00
header.go verbage to inform someone that looks 2025-01-09 06:05:38 -06:00
main.go rename 2025-01-09 06:09:09 -06:00
marshal.go marshal is converted to using the protobuf 2025-01-09 05:00:29 -06:00
newsort.go rename 2025-01-09 06:09:09 -06:00
protoParse.go mutex's are being added to the protoc pb.go file 2025-01-09 05:49:23 -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 all functions are passed the informationn in the protobuf 2025-01-09 05:20:00 -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.