*: reflow comments to 80 characters
This reformats the entire Metropolis codebase to have comments no longer
than 80 characters, implementing CR/66.
This has been done half manually, as we don't have a good integration
between commentwrap/Bazel, but that can be implemented if we decide to
go for this tool/limit.
Change-Id: If1fff0b093ef806f5dc00551c11506e8290379d0
diff --git a/intellij/localconfig/localconfig.go b/intellij/localconfig/localconfig.go
index fd44d9a..de34f0e 100644
--- a/intellij/localconfig/localconfig.go
+++ b/intellij/localconfig/localconfig.go
@@ -14,16 +14,18 @@
// See the License for the specific language governing permissions and
// limitations under the License.
-// localconfig modifies the project's IntelliJ config to include project-specific settings. This is usually done by
-// checking in the .idea directory, but we do not want to do this: it conflicts with the Bazel plugin's way of
-// conducting its workspace business, lacks backwards compatibility, and is a common source of spurious Git diffs,
-// especially when the IDE/JDK/random plugins are updated and team members run different versions.
+// localconfig modifies the project's IntelliJ config to include project-specific
+// settings. This is usually done by checking in the .idea directory, but we do not
+// want to do this: it conflicts with the Bazel plugin's way of conducting its
+// workspace business, lacks backwards compatibility, and is a common source of
+// spurious Git diffs, especially when the IDE/JDK/random plugins are updated and
+// team members run different versions.
//
-// Instead, we use the officially supported way of shipping IntelliJ Bazel project configs - a .bazelproject file that
-// can be imported using the Bazel project import wizard, with local configs. We then use this tool to mangle the local
-// configs to add additional custom configuration beyond run configurations. This avoids merge conflicts and allows us
-// to intelligently handle schema changes.
-//
+// Instead, we use the officially supported way of shipping IntelliJ Bazel project
+// configs - a .bazelproject file that can be imported using the Bazel project
+// import wizard, with local configs. We then use this tool to mangle the local
+// configs to add additional custom configuration beyond run configurations. This
+// avoids merge conflicts and allows us to intelligently handle schema changes.
package main
import (
diff --git a/intellij/localconfig/watchers/filewatchers.go b/intellij/localconfig/watchers/filewatchers.go
index f31a26a..dd1810c 100644
--- a/intellij/localconfig/watchers/filewatchers.go
+++ b/intellij/localconfig/watchers/filewatchers.go
@@ -86,7 +86,8 @@
return fmt.Errorf("failed to serialize: %w", err)
}
- // Atomic write is needed, IntelliJ has inotify watches on its config and reloads (but not applies) instantly.
+ // Atomic write is needed, IntelliJ has inotify watches on its config and reloads
+ // (but not applies) instantly.
tmpPath := filename + ".tmp"
defer os.Remove(tmpPath)
if err := ioutil.WriteFile(tmpPath, []byte(xml.Header+string(b)), 0664); err != nil {
@@ -99,7 +100,8 @@
return nil
}
-// RewriteConfig adds our watchers to projectDir's watchers config, overwriting existing entries with the same name.
+// RewriteConfig adds our watchers to projectDir's watchers config, overwriting
+// existing entries with the same name.
func RewriteConfig(projectDir string) error {
template, err := readConfig(path.Join(projectDir, templatePath))
if err != nil {