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
  • 11 years ago
  • 58 minutes ago
  • 11 years ago

Installs

  • Total 1K
  • Win 554
  • Mac 360
  • Linux 142
May 30 May 29 May 28 May 27 May 26 May 25 May 24 May 23 May 22 May 21 May 20 May 19 May 18 May 17 May 16 May 15 May 14 May 13 May 12 May 11 May 10 May 9 May 8 May 7 May 6 May 5 May 4 May 3 May 2 May 1 Apr 30 Apr 29 Apr 28 Apr 27 Apr 26 Apr 25 Apr 24 Apr 23 Apr 22 Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16
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 //.