Closed soc-se-bot closed 7 months ago
As per discussion just now, there will be a few possible cases during the import process from JSON to DailyMedicationmanager
(DailyMgr)
The core idea is to preserve (past) daily medication data for the future implementation of being able to retrieve taking of medication history (Name, taken, dosage), even if the medication no longer exist in the MedicationManager
(MedMgr). On that note, DailyMgr will have to refer to MedMgr on a best-effort basis rather than a fail-if-not-found idea. (Remove the assumption that what is on the today list is also on the main list)
Possible cases of corruption
Case 1.1: JSON is corrupt and is unable to recover any data but the daily txt file is not corrupt
Case 1.2: JSON is partially corrupt (able to recover some data) but the daily txt file is not corrupt
Case 2: Json is not corrupt, Daily txt file is corrupt
Things of things to mention in the User Guide
list -t
command, mention that the all
and today
results are separate; that information of one does not affect the information of the other.Mention with comments below whichever part is closed once implemented
Classified this bug as low as a user editting the JSON file may not necessarily be a very common case.
Note that i went to set the json file to an invalid file.
The
list -l today
initially works, however, after editing the JSON file to be invalid and starting the app again,list -t today
returns an exception.Labels:
severity.Low
type.FunctionalityBug
original: itsmejr257/ped#9