Please keep settings grouped logically #7178
Labels
config
Configuration related issues
documentation
Issue related to documentation
meta
Issue related to topics which state a more general problem or discussion
wontfix
Issue won't be fixed
Is your feature request related to a problem you are facing?
I'm new to Jitsi and trying to figure out the various settings in its various config files. I've read the Handbook, but haven't found a page that explains the settings, so I have to rely on the comments in
interface_config.js
andconfig.js
. (If there are other config files, I don't know yet, because, again, they aren't clearly explained in the Handbook - jitsi/handbook#61).The problem is that all settings in
interface_config.js
were recently sorted in alphabetical order. Before, these settings were grouped logically. For example, if we wanted to configure branding and watermarks, the settings were in one place (and other related settings could be brought to the group):Now, watermark and branding settings are spread apart, and other settings come between them:
This separation makes it even harder to figure out what the settings do and how they relate.
The only argument I've seen for sorting this file is that it makes it easier to compare it across different deployments. I think that's,
sort
before comparing them.Given the current situation, Jitsi has a large influx of new users.
I don't think confusing most new users by sorting settings alphabetically, outweighs the minor benefit for occasionally comparing the file across multiple deployments, which can be solved by piping them through
sort
.Describe the solution you'd like
Revert the commit that sorted the settings in
interface_config.js
, and apply subsequent commits that did materially improve the file (e.g. #7169, #7170, #7172).The settings in
config.js
are also grouped logically, and that's very helpful. Why not preserve that convention?The text was updated successfully, but these errors were encountered: