chore: Renames settings.json to be settings.recommendation.json and enhance .gitignore content

Jacksunwei · copybara-github · commit 02d4a5f178c0 · 2025-10-03T13:22:40.000-07:00
- It's not a good practice to enforce settings.json, since each developer may have different settings of their specific IDE env.
- It's no-harm to have a recommended template to start with.
- `extensions.json` is good, since it gives suggestion on the useful vs code extensions.

PiperOrigin-RevId: 814806918
diff --git a/.gitignore b/.gitignore
@@ -1,2 +1,32 @@
+# Compiled class files
+*.class
+
+# Log files
+*.log
+
+# Package Files
+*.jar
+*.war
+*.nar
+*.ear
+*.zip
+*.tar.gz
+*.rar
+
+# Maven target directory
 target/
-.idea
+.mvn/
+
+# IntelliJ IDEA files
+.idea/
+*.iml
+*.ipr
+*.iws
+out/
+
+# VS Code files
+.vscode/settings.json
+
+# OS-specific junk
+.DS_Store
+Thumbs.db
diff --git a/.vscode/settings.recommended.json b/.vscode/settings.recommended.json
@@ -1,4 +1,6 @@
 {
+  // A recommended set of settings for VS Code.
+  //
   // formatOnType and formatOnPaste is a very bad idea for slow formatters
   // (such as an external Google Java Format invocation exec), so just on Save:
   "editor.formatOnSave": true,

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,6 @@`
`1`	`1`	`{`
	`2`	`+ // A recommended set of settings for VS Code.`
	`3`	`+ //`
`2`	`4`	`// formatOnType and formatOnPaste is a very bad idea for slow formatters`
`3`	`5`	`// (such as an external Google Java Format invocation exec), so just on Save:`
`4`	`6`	`"editor.formatOnSave": true,`