0049584: Product modifiers should be moved to product.configuration.modifiers to allow deactivating them

Description

Currently when a modifier or modifier group is deactivated, it will not be present in the masterdata, and as such it is not possible to register a renderer for it in ob-init.js. Moving the configuration from current config:
product.configuration: {
  'AD298312DAF293801A1092310EE23': {...},
  'BC123132DAF293801A1092310EE23': {...}
}

to its own subobject in product.configuration.modifiers would simplify things:
product.configuration: {
  modifiers: {
    'AD298312DAF293801A1092310EE23': {...},
    'BC123132DAF293801A1092310EE23': {...}
  }
}

This would allow registering only 1 renderer, for the key string "modifiers", and will not be affected when a modifier is not present in the masterdata because it has been deactivated.

Steps To Reproduce

In description

Proposed Solution

Move configuration to be in a subobject of product.configuration, this requires checking all the places where it is being accessed or modified and take into account the new placement of modifiers.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

defect

0049533

closed

AugustoMauch

JIRA 3074 - After opening certain tickets in sales history, a blocking error appears (and clean cache needed to unblocked)

Notes
(0138419) cberner (viewer) 2022-06-16 13:58	A workaround has been applied in issue 49533, but this is the proper fix to the issue.

Issue History
Date Modified	Username	Field	Change
2022-06-16 13:57	cberner	New Issue
2022-06-16 13:57	cberner	Assigned To	=> Retail
2022-06-16 13:57	cberner	OBNetwork customer	=> No
2022-06-16 13:57	cberner	Triggers an Emergency Pack	=> No
2022-06-16 13:58	cberner	Relationship added	related to 0049533
2022-06-16 13:58	cberner	Note Added: 0138419
2022-06-21 16:41	cberner	Type	defect => feature request