Open spinoandraptos opened 10 months ago
Thank you for your response.
Will take note of this, and make the necessary improvements in the future.
It would be good if the program could tell what is wrong in the file.
As of our current iteration, it is beyond our scope.
But thank you for your idea.
Team chose [response.NotInScope
]
Reason for disagreement:
This bug impacts are too serious to be pushed to future iterations to rectify, and it is not mentioned in the UG that users cannot directly manipulate the text file to update data. Imagine a scenario for a normal wildlife reserve clerk who already has hundreds of entries and decided to manually add in some entries from a new record by copy pasting all into the text file in one go (as it is faster than inputting one by one in CLI), and in the midst of doing so accidentally created a duplicate of one of the entries while copy pasting. In the huge list of entries it may not be easy to spot the error, and on starting the program the above error occurs and the clerk is at a loss of what to do as he is unsure of what is corrupted in the huge list of entries. Spending time to check through the list one by one is a major inconvenience for the clerk and may delay critical operations on data entries, making the impact of such a vague error message something that should be prioritised. As such, it should not be a not in scope bug.
Message only shows file is corrupted, but does not help user understand why so.