- changed milestone to Coding Convention Adherence
Replace semi-random Preference node names by class name to be more specific
USE CASE: WHAT DO YOU WANT TO DO?
Creating a new Preferences node for a class or accessing one.
STEPS TO REPRODUCE AN ISSUE (OR TRIGGER A NEW FEATURE)
CURRENT BEHAVIOR
Throughout the software when Preferences nodes are created or accessed, custom semi-random names are used.
EXPECTED BEHAVIOR
Preferences nodes for a class carry the name of the specific class which they are created for (e.g. in setConfigNode() methods).
DEVELOPERS ONLY SECTION
SUGGESTED CHANGE (Pseudocode optional)
Replace custom chosen names such as
Preferences.node("FooClassNode")
by
Preferences.node(this.getClass().getName())
FILES AFFECTED (where the changes will be implemented) - developers only
all files working with Preferences nodes
LEVEL OF EFFORT - developers only
medium (only due to spread of Preferences code, possibly just a minor issue)
COMMENTS
Comments (4)
-
-
- changed component to Coding Convention Adherence
-
- removed milestone
Removing milestone: Coding Convention Adherence (automated comment)
-
- changed version to beta2
- Log in to comment