Can't override core mapWidgetTypes

[abea]

Question or comment

Please include as much detail as possible so we can help more quickly.

• The way it is written, self.options.mapWidgetTypes takes any user-entered configuration, spreads it, then adds core widget config. This prevents users from overriding the core widget mapping. For image widgets it could be especially useful to be able to identify a different widget type and data structure

Details

Current mapping:

    self.options.mapWidgetTypes = {
      ...self.options.mapWidgetTypes,
      'apostrophe-rich-text': '@apostrophecms/rich-text',
      'apostrophe-images': async (widget) => ({
        ...widget,
        type: '@apostrophecms/image',
        imageFields: widget.relationships,
        imageIds: (widget.pieceIds || []).slice(0, 1)
      }),
      'apostrophe-video': '@apostrophecms/video',
      'apostrophe-html': '@apostrophecms/html'
    };

content-upgrader/index.js

Lines 29 to 40 in f405ce4

	self.options.mapWidgetTypes = {
	...self.options.mapWidgetTypes,
	'apostrophe-rich-text': '@apostrophecms/rich-text',
	'apostrophe-images': async (widget) => ({
	...widget,
	type: '@apostrophecms/image',
	imageFields: widget.relationships,
	imageIds: (widget.pieceIds || []).slice(0, 1)
	}),
	'apostrophe-video': '@apostrophecms/video',
	'apostrophe-html': '@apostrophecms/html'
	};