Open nus-pe-bot opened 2 weeks ago
Dear Tester, we would like to label this issue as NotInScope.
This is a valid and good feature to include for a future iteration of our application, but it is currently not implemented as there were much higher priority features to implement for the edit command, and this is relatively low priority in comparison.
For v2.1, we prioritised allowing the user to edit the different types of parameters independently (e.g. editing only name attribute without changing anything else, editing both ingredients and cuisine type of recipe), as well as the ability to delete optional parameters of a recipe (cuisine type, time taken). Those streamlined the usage of the edit command a lot and we feel those features are much more crucial for the user than being able to augment individual steps, thus prioritising them first.
Editing individual steps in a recipe is also a dangerous operation, as the user could want to insert a new step, overwrite an existing step, or a delete a step, and the ordering of the steps mustn’t be jumbled by this operation, while also checking that what the user is trying to do is valid (e.g. user trying to edit a non-existing step should be invalid). Given this consideration, a lot of care has to be taken to implement this feature in a safe and user-friendly manner, which mandates a lot of design consideration and safety testing, and in consideration with its lesser priority, it was left out of the v2.1 scope.
Given that, it isn’t currently in the scope of our project (we have also made it clear in our documentation that the current version of our application requires all recipe steps be edited together without support for only augmenting individual steps), but we thank you for your feedback.
--
Takes far more time if I want to just edit 1 ingredient/step when I have to retype the entire list
[original: nus-cs2113-AY2425S1/pe-interim#542] [original labels: type.FeatureFlaw severity.Low]