Skip to content

global parameters which assumed to be plugin parameters #582

@danceb

Description

@danceb

While checking all config parameters from the docs at [1] and [2] agains my config.json for switching to 2026-lts I came across a bunch of global parameters which seem to be better defined as specific plugin parameters. In addition there are general and plugin specific parameters with the same effect.

LayerTree

general plugin specific
allowLayerTreeSeparators allowLayerTreeSeparators
addLayerSeparator (no effect)
allowRemovingThemeLayers allowRemovingThemeLayers
allowReorderingLayers -
disableImportingLocalLayers -
flattenLayerTreeGroups flattenGroups
importLayerUrlPresets -
preventSplittingGroupsWhenReordering -

Topbar - Search Parameters

general plugin specific
searchFilterRegions -
searchThemeLayers -
searchThemes -

ThemeSwitcher

general plugin specific
allowAddingOtherThemes hideAddThemeButton
hideAddThemeLayersButton

So, why are these parameters defined as global ones? I think it would be a good enhancement to harmonize this parameters and define plugin specific settings within the plugin config blocks as there is no need for them to be global.
As the change to an new lts version is a good moment for such thing, as it could be clearly documented in the changelog, unfortunately we just had such version change and the next one would be in about a year ...

--
[1] https://qwc-services.github.io/2026-lts/configuration/ViewerConfiguration/#global-settings
[2] https://qwc-services.github.io/2026-lts/references/qwc2_plugins/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions