Is your feature request related to a problem?
Currently, if the default config and the ServerConfig struct are updated the new fields won't be serialized to the existing config. Unless the user inserts the value themselves or deletes the config, the new value will always use the default one.
Describe the solution / feature you'd like.
If a field is missing from the config, the default value and the comments associated with that field should be serialized to the existing config. This makes it easier for users to see if there's any new config values that they have available to them after an update.
Alternatives you've considered.
N/A
Additional Context
No response
I have confimed that...
Is your feature request related to a problem?
Currently, if the default config and the ServerConfig struct are updated the new fields won't be serialized to the existing config. Unless the user inserts the value themselves or deletes the config, the new value will always use the default one.
Describe the solution / feature you'd like.
If a field is missing from the config, the default value and the comments associated with that field should be serialized to the existing config. This makes it easier for users to see if there's any new config values that they have available to them after an update.
Alternatives you've considered.
N/A
Additional Context
No response
I have confimed that...