You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to propose that we standardize our constants file to use upper snake case, such as MY_CONSTANT_VALUE instead of either camel case myConstantValue or kabab case my-constant-value. This is the java default pattern and conveniently the one that sonarlint enforces.
I'd also propose we drop the c++ pattern of prepending constants with k or k_ as they will already be visually distinct in the code. C++ uses that pattern because it reserves upper snake case for use with compile time replacements, something that java does not have.
This is very low priority, but a great small project for someone to carefully do when they need a break from their complex work – say writing commands for example.
please use the symbol rename feature, this is much more reliable then manual renaming
I'd like to propose that we standardize our constants file to use upper snake case, such as
MY_CONSTANT_VALUE
instead of either camel casemyConstantValue
or kabab casemy-constant-value
. This is the java default pattern and conveniently the one that sonarlint enforces.I'd also propose we drop the c++ pattern of prepending constants with
k
ork_
as they will already be visually distinct in the code. C++ uses that pattern because it reserves upper snake case for use with compile time replacements, something that java does not have.This is very low priority, but a great small project for someone to carefully do when they need a break from their complex work – say writing commands for example.
please use the symbol rename feature, this is much more reliable then manual renaming
Constants file for reference
The text was updated successfully, but these errors were encountered: