Open seanngja opened 3 days ago
[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Thanks for raising this issue. This is actually the expected behavior. File parsed in and file generated from the program are entirely different. Tester seem to stick with the idea of iP
where data generated through the program will be saved and allowed to be pass through the program again (Closed Loop System). However, as mentioned at the start of the UG under Pre-Usage Guidelines
, the allocation results file is NOT meant to be re-inputted into the program. The program is designed to have one input and one output where the output cannot be used as input (Open Loop System). The UG also provided some examples on what are the accepted file types and format and even provided test files for the users to experiment with. Our team believes that we handled this misuse case appropriately by prompting the error sufficiently to the user and allowing them to continue using the program.
[The team marked this bug as a duplicate of the following bug]
uploading a csv file that was generated by the program fails to load without editing
below is the csv file without editing
[original: nus-cs2113-AY2425S1/pe-interim#290] [original labels: severity.Medium type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
Thanks for raising this issue. This is actually the expected behavior. File parsed in and file generated from the program are entirely different. Tester seem to stick with the idea of
iP
where data generated through the program will be saved and allowed to be pass through the program again (Closed Loop System). However, as mentioned at the start of the UG underPre-Usage Guidelines
, the allocation results file is NOT meant to be re-inputted into the program. The program is designed to have one input and one output where the output cannot be used as input (Open Loop System). The UG also provided some examples on what are the accepted file types and format and even provided test files for the users to experiment with. Our team believes that we handled this misuse case appropriately by prompting the error sufficiently to the user and allowing them to continue using the program.
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your reason]
This is without making any attempts to modify the txt file.