ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Proto​Buf​Code​Formatter

by DirkBrand ST2

Sublime plugin that allows auto-formatting of Protocol Buffer Code.

Labels formatting

Details

  • 1.0.5
  • github.​com
  • github.​com
  • 12 years ago
  • 58 minutes ago
  • 12 years ago

Installs

  • Total 1K
  • Win 554
  • Mac 360
  • Linux 142
Aug 27 Aug 26 Aug 25 Aug 24 Aug 23 Aug 22 Aug 21 Aug 20 Aug 19 Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5 Aug 4 Aug 3 Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Mac 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

ProtoBufCodeFormatter_Sublime

Sublime-Text-2 plugin that allows auto-formatting of Protocol Buffer Code on save.

Installation

ProtoBufCodeFormatter is available via Package Control and can be found as ProtoBufCodeFormatter.

*Important this plugin uses the GOPATH, please set it in Settings - User.

Requirements

  • Golang v1.0 or higher
  • Correctly set PROTOPATH, GOROOT and GOBIN in the Settings - User.

Open Settings - User under Preferences/Package Settings and edit to contain the correct path information. Add variable GOBIN and enter the location of your Go Binary. Add variable PROTOPATH and enter any locations of Protocol Buffers that are imported by your protocol buffers. Optionally add a GOROOT variable to show the location of your Go workspace. Look at Settings - Default as an example.

Limitations

  1. Formatter cannot preserve order of structures. The order is pre-determined.

  2. For comments, outer extend' groups are logically grouped together, so inner comments are lost.

  3. Style of comments are not preserved (/* */ vs. //), so both single-line and multi-line comments are shown with //.