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

Openbravo Issue Tracking System - POS2

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0049584

POS2

POS

public

2022-06-16 13:57

2022-06-21 16:41

Reporter

cberner

Assigned To

Retail

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

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.

Additional Information