aboutsummaryrefslogtreecommitdiffhomepage
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorNassim Jahnke <[email protected]>2024-05-09 15:10:27 +0200
committerNassim Jahnke <[email protected]>2024-05-09 15:10:27 +0200
commitab2a85a35f8749bbb59132cf0d203213c9ef10f3 (patch)
treee928d1df8e2e61b176ba6a85bc9de51d04953f03 /CONTRIBUTING.md
parent5729b294eef2ffde690f73c5b14a64a31f301084 (diff)
downloadPaper-ab2a85a35f8749bbb59132cf0d203213c9ef10f3.tar.gz
Paper-ab2a85a35f8749bbb59132cf0d203213c9ef10f3.zip
[ci skip] Clarify var entry in contributing file
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index acba91f491..18dacf9208 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -237,10 +237,10 @@ into most IDEs and formatters by default. There are a few notes, however:
There are exceptions, especially in Spigot-related files
- When in doubt or the code around your change is in a clearly different style,
use the same style as the surrounding code.
-- `var` usage is heavily discouraged, as it makes reading patch files a lot harder
-and can lead to confusion during updates due to changed return types. The only
-exception to this is if a line would otherwise be way too long/filled with hard
-to parse generics in a case where the base type itself is already obvious
+- Usage of the `var` keyword is heavily discouraged, as it makes reading patch files
+a lot harder and can lead to confusion during updates due to changed return types.
+The only exception to this is if a line would otherwise be way too long/filled with
+hard to parse generics in a case where the base type itself is already obvious
### Imports
When adding new imports to a class in a file not created by the current patch, use the fully qualified class name