`add -d` command should also check if the relevant item has the correct unit of measurement.

[thony-ui]

• Description:
  When entering the add -d command, it should check if the item has the corresponding unit of measurement. It does not make sense for an item of type rice to have the unit of measurement L because rice is in solid state and L is reserved for items in the liquid state.

• Steps to Reproduce:

  1. Enter the command add -d on/19-12-2022 08:00 s/2 pro/rice q/50 L c/50.20

• Expected Result:
  The command should fail to execute because rice has no unit of measurement L.

• Actual Result:
  The command executes successfully as shown from the screenshot below.

[nus-pe-script]

Team's Response

Thank you for bringing this issue to our attention. While it is a valid observation that certain products may have typical or logical units of measurement, implementing a feature to validate the nature of the product against its unit of measurement is currently outside the scope of our application. This is due to the complexity and the additional resources required to maintain a comprehensive mapping of product types to valid units, which is not a priority for the current version (v1.6). Additionally, it is reasonable to expect that our users may add products that are unique to their shop, making it impractical to determine or enforce what units of measurement are valid for those specific products.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: The absence of this functionality in the User Guide (UG) and Developer Guide (DG), along with its exclusion from the future enhancements section, highlights a feature flaw. Allowing users to label something as a liquid when it is actually in a solid state undermines the accuracy and reliability of the application. This is particularly problematic because if users mistakenly input the wrong data, they could misidentify the product, leading to confusion or even critical errors depending on the use case. Without proper guidance in the UG/DG or plans to address this in future updates, the feature feels incomplete and unpolished.

---