Ah, I see. I think I can understand why that was done initially, but since
using UPDATE_HORIZON_CONFIG is already going beyond the scope of the enabled
file since its directly affecting an exposed setting, I think we should just
use the setting (and document it appropriately in the settings.rst)
On 3 August 2016 at 00:32, Rob Cresswell
wrote:
> Hi all,
>
> So we seem to be adopting a pattern of using UPDATE_HORIZON_CONFIG in the
> enabled files to add a legacy/angular toggle to the settings. I don't like
> this, because in settings.py the enabled files are processed *after*
> local_setti
Hi all,
So we seem to be adopting a pattern of using UPDATE_HORIZON_CONFIG in the
enabled files to add a legacy/angular toggle to the settings. I don't like
this, because in settings.py the enabled files are processed *after*
local_settings.py imports, meaning the angular panel will always be e