Actions
Refactor #7361
open![Author: Anonymous](/images/anonymous.png?1697023634)
functionality of Setting class should be broken up into multiple classes, one per setting type
Status:
New
Priority:
Normal
Assignee:
-
Category:
Settings
Target version:
-
Description
Currently the class is very procedural, with multiple methods using conditional logic to handle different setting types.
No data to display
Actions