Upstream/Paper
1
0
Fork 0
mirror of https://github.com/PaperMC/Paper.git synced 2024-11-24 11:38:29 +01:00
Code Issues Projects Releases Wiki Activity

[ci skip] Clarify var entry in contributing file

Browse Source
This commit is contained in:
Nassim Jahnke 2024-05-09 15:10:27 +02:00
parent 5729b294ee
commit ab2a85a35f
No known key found for this signature in database
GPG Key ID: EF6771C01F6EF02F
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING.md
View File

@ -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 There are exceptions, especially in Spigot-related files
- When in doubt or the code around your change is in a clearly different style, - When in doubt or the code around your change is in a clearly different style,
use the same style as the surrounding code. use the same style as the surrounding code.
- `var` usage is heavily discouraged, as it makes reading patch files a lot harder - Usage of the `var` keyword is heavily discouraged, as it makes reading patch files
and can lead to confusion during updates due to changed return types. The only a lot harder and can lead to confusion during updates due to changed return types.
exception to this is if a line would otherwise be way too long/filled with hard The only exception to this is if a line would otherwise be way too long/filled with
to parse generics in a case where the base type itself is already obvious hard to parse generics in a case where the base type itself is already obvious
### Imports ### Imports
When adding new imports to a class in a file not created by the current patch, use the fully qualified class name When adding new imports to a class in a file not created by the current patch, use the fully qualified class name