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
In #612 we migrate theme names and add an alias table which allows the old names to continue working.
This issue is to track whether in future we remove this theme aliases dict - possibly in one major release first as a fatal error at loading, indicating more strongly that the theme should be replaced (or automatically updated in the file, or other location?) - and then in the next significant release actually removing the aliases and treating the old names as invalid.
The text was updated successfully, but these errors were encountered:
A message is output on loading indicating if the theme loading is an
alias of another theme.
Theme aliases may be removed in future (zulip#648).
Tests updated.
A message is output on loading indicating if the theme loading is an
alias of another theme.
Theme aliases may be removed in future (#648).
Tests updated.
Automatically updating would be the source of the provided configuration; I'm wary of doing this as we're touching user config, but we're not yet at a stage where we need to consider this change. This may be less problematic after #678 if the config is separated from profiles and we generate a guaranteed new proposed config file.
In #612 we migrate theme names and add an alias table which allows the old names to continue working.
This issue is to track whether in future we remove this theme aliases dict - possibly in one major release first as a fatal error at loading, indicating more strongly that the theme should be replaced (or automatically updated in the file, or other location?) - and then in the next significant release actually removing the aliases and treating the old names as invalid.
The text was updated successfully, but these errors were encountered: