Kademlia: Created page with "General rules to support a large amount of config settings via commands # We should not support everything with user.getXYZ() -> value. We generate way to many methods # We s..."

2020-03-23T22:42:56Z

Created page with "General rules to support a large amount of config settings via commands # We should not support everything with user.getXYZ() -> value. We generate way to many methods # We s..."

New page

General rules to support a large amount of config settings via commands

# We should not support everything with user.getXYZ() -> value. We generate way to many methods
# We should not create a private variable for every setting. This take to much effort to maintain and results in large jsons even with every setting set to the default
# We cannot use Map<String, Setting> as it would be too slow. We need near direct access.

Current System:

# Enum-Id based cache array for each user allows direct access
# Enum allows (often times) safe access / casting is limited to internal
# Hundreds of options will still work the same

Open:

We need good rules to check values against. These should be reused. We need them in ChangeUserSettingOptionAction at least for chat infos on errors

How do we integrate permissions for each value?

UserCommands - Revision history

Kademlia: Created page with "General rules to support a large amount of config settings via commands # We should not support everything with user.getXYZ() -> value. We generate way to many methods # We s..."