Add a hint on how to override local developed mapcontrols within config.template.js

[Raruto]

As per v3.8, through the config.js file it is possible to extend the "initConfig->group->plugins" variable for custom plugin development (NB additively, i.e. without completely wiping the configuration received from the server):

g3w-client/config.template.js

Lines 8 to 12 in 15d3241

	const G3W_PLUGINS = [ // override "initConfig->group->plugins" attribute for custom plugin development
	// "your-plugin-folder-name-1",
	// "your-plugin-folder-name-2",
	// "your-plugin-folder-name-3",
	];

Find out a clean and smart way (ref. variable name) to do the same with mapcontrols to extend / list the mapcontrols we intend to develop locally.

If effective, in the near future, this method could also be used to write specific tests for a single mapcontrol.

Draft implementation

// config.js

const G3W_CONTROLS = [ // overwrite "initConfig->group->mapcontrols" attribute for custom mapcontrol development
  // "zoomtoextent",
  // "zoom",
  // "zoombox",
  // "query",
  "querybbox",
  "querybypolygon",
  "querybydrawpolygon",
  // "overview",
  // "scaleline",
  // "geolocation",
  // "nominatim",
  // "addlayers",
  // "length",
  // "area",
  // "mouseposition",
  // "scale",
  // "screenshot",
  // "geoscreenshot"
];

...

  devConfig: function() {
    g3wsdk.core.ApplicationService.once('initconfig', () => {
      initConfig.group.mapcontrols = G3W_CONTROLS || initConfig.group.mapcontrols;
    });
  }

Related to:

• Add new map control querybydrawpolygon #341
• Add src/index.dev.js and src/index.dev.js (app entrypoints) #325
• Move src/app/dev/index.js into config.template.js #89