Proposed Solution for”Add to Cart” Function and Quantity Field Issue

 ✅1. Add “Add to Cart” Button & Quantity Updating

Analysis:

• The implementation allows for adding an “Add to Cart” button next to each item in the overview list and search results.
• The proposed usage of the Frontend Extensibility API’s AddLine() function is not applicable since the project follows the Elbrus version.
• Instead, LiveOrderModel. getInstance(). addLine(selected_line). done(function () { }) should be used for cart updates.
• The selected_line must follow the required format to ensure correct functionality:

addLine: function addLine(line_data) {

var item = {

internalid: line_data.item.internalid.toString(),

quantity: _.isNumber(line_data.quantity) ? parseInt(line_data.quantity, 10) : 1,

options: this.parseLineOptionsToCommerceAPI(line_data.options)

};

if (this.isPickupInStoreEnabled && line_data.fulfillmentChoice === 'pickup' && line_data.location) {

item.fulfillmentPreferences = {

fulfillmentChoice: 'pickup',

pickupLocationId: parseInt(line_data.location, 10)

};

}

var line_id = ModelsInit.order.addItem(item);

return line_id;

}

• If the client requires multiple items to be added at once, an “Add Selected Items to Cart” button should be placed beside the “Save Changes” button.
• In such a scenario, the addLines() function should be used instead of addLine() to handle batch additions.

Verification:

• Validate that the button placement and UI responsiveness align with the existing layout.
• Confirm that quantity updates function correctly without duplicate cart entries. in case of duplication, we have to make use of the updateline method

updateLine: function updateLine(line_id, line_data) {

var lines_sort = this.getLinesSort(), current_position = _.indexOf(lines_sort, line_id), original_line_object = ModelsInit.order.getItem(line_id, [

'quantity',

'internalid',

'options',

'fulfillmentPreferences'

]);

this.removeLine(line_id);

if (!_.isNumber(line_data.quantity) || line_data.quantity > 0) {

var new_line_id;

try {

new_line_id = this.addLine(line_data);

} catch (e) {

var roll_back_item = {

item: { internalid: parseInt(original_line_object.internalid, 10) },

quantity: parseInt(original_line_object.quantity, 10)

};

if (original_line_object.options && original_line_object.options.length) {

roll_back_item.options = {};

_.each(original_line_object.options, function (option) {

roll_back_item.options[option.id.toLowerCase()] = option.value;

});

}

new_line_id = this.addLine(roll_back_item);

e.errorDetails = {

status: 'LINE_ROLLBACK',

oldLineId: line_id,

newLineId: new_line_id

};

throw e;

}

lines_sort = _.without(lines_sort, line_id, new_line_id);

lines_sort.splice(current_position, 0, new_line_id);

this.setLinesSort(lines_sort);

}

},

• Test edge cases such as multiple simultaneous additions and rapid updates.
• In this functionality, we have to add an input box for quantity and add to cart button along with each item so we have to confirm the UI of the listing section in both the overview list and update list

✅2. Prevent Inventory Updates for Blank Quantity Fields

Analysis:

• The saveChanges function in Inventory.Management. Lookup.View.js can be modified to prevent inventory updates for items with blank quantity fields.
• This can be achieved by adding a validation condition within the _.filter function:

var activeCollection = _.filter(self.itemCollection, function (item) {

return !!item.isSelected && !isNaN(item.quantity) && item.quantity !== null;

});

• This ensures that only items with valid quantities are processed, preventing erroneous inventory updates.
• If all selected items have invalid quantities, the system will trigger an appropriate warning message to guide the user.
• Updating the UI message to explicitly instruct users to check item quantities would enhance usability.

Verification:

• Confirm that inventory updates are blocked when quantity fields are blank or contain invalid values.
• Validate that appropriate user messages are displayed when such cases occur.
• Test bulk update scenarios to ensure correct handling of valid and invalid entries.

Deliverables:

• A verified and confirmed solution ensuring that:
• The “Add to Cart” functionality works as expected.
• Inventory updates do not occur for blank quantity fields.

Conclusion: The proposed solution is viable with necessary modifications to accommodate Elbrus version limitations. The use of LiveOrderModel instead of the Frontend Extensibility API is essential for proper cart updates. Additionally, the inventory update prevention logic is correctly implemented and ensures data integrity. Further UI refinements and user prompts will improve the overall experience.