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
Config-parsing code already supports nested keys but this feature is explicitly disabled in code for more than one nesting level.
API also supports nested keys, see IConfigEntry::getSubConfig method.
It seems we could safely enable this feature (and there is users asking for it)
Example of nested keys (could be used in plugins.conf):
Strongly speaking, wrong parsing of nested keys is a different issue, but enabling of not working code is a nonsense therefore i decided to not create new ticket.
Submitted by: @hvlad
Config-parsing code already supports nested keys but this feature is explicitly disabled in code for more than one nesting level.
API also supports nested keys, see IConfigEntry::getSubConfig method.
It seems we could safely enable this feature (and there is users asking for it)
Example of nested keys (could be used in plugins.conf):
Config = MyPluginConfig {
Key1 = Val1
Key2 = Val2 {
SubKey = Val
Subkey2 = {
...
}
}
}
currently, such configuration is parsed as set of plain keys.
Commits: 25177b5 2825af9 11b0bf7 50447a5
The text was updated successfully, but these errors were encountered: