Go to file
Jeff Carr d67c2eb3a2 cleanup output more 2025-01-09 04:03:30 -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 parse for all the structs 2025-01-08 20:52:47 -06:00
README add example. and forgot the GPL! 2024-12-31 13:24:00 -06:00
addMutex.go make a protofile for the app itself 2025-01-08 19:45:48 -06:00
argv.go make a protofile for the app itself 2025-01-08 19:45:48 -06:00
auto.proto rename file 2025-01-09 03:44:09 -06:00
control add control file 2024-12-18 03:02:44 -06:00
header.go make a protofile for the app itself 2025-01-08 19:45:48 -06:00
main.go cleanup output more 2025-01-09 04:03:30 -06:00
marshal.go duh. TRUNC files 2024-12-11 13:50:38 -06:00
protoParse.go cleanup output more 2025-01-09 04:03:30 -06:00
protoc.go make a protofile for the app itself 2025-01-08 19:45:48 -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.