Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Record JSON Storage Format to DG #132

Merged
merged 13 commits into from
Oct 27, 2023

Conversation

longnguyentan
Copy link

Add Record JSON Storage Format to DG

Key Changes:

  • Added a new section in the Developer Guide detailing the JSON representation of the Record class.
  • Provided an illustrative example with a breakdown of each JSON field for clarity.
  • Highlighted default values associated with certain fields when no data is available.

longnguyentan and others added 12 commits October 18, 2023 14:07
Revert "Update project from team repo"
Implement JsonAdaptedRecord to enable JSON serialization for patient records.
Update JsonSerializableAddressBook to work with new serialization.
Enhance AddressBook model to support new serialization functionality.
Introduce UniqueRecordList for ensuring record uniqueness.
The A&E current UI does not match with the team's design.
Update the FXML files to update the design.
- Test default constructor for Record.
- Validate initialization with default values for fields.
- Test setters and getters for initialObservations, diagnosis, treatmentPlan.
- Ensure correct behavior of equals method.
- Detailed the JSON representation of the `Record` class.
- Provided an example JSON format with explanations for each field.
- Highlighted the default values used for certain fields when no data is provided.
Copy link

@thienmy0 thienmy0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 👍 Mainly changes on DG, UI, integrating Record into Storage & some checkstyle fixing. This PR seems to include the changes made from your other 3 PRs too so might want to check on that.

import seedu.address.storage.Storage;
import seedu.address.storage.StorageManager;
import seedu.address.storage.UserPrefsStorage;
import seedu.address.storage.*;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps * import statements should be avoided?

}
```

#### Explanation:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like how you added the explanation about how you integrated Record into Storage!

@@ -3,17 +3,48 @@
}

#copyButton {
-fx-background-color: dimgray;
-fx-background-color: #3C4EEF;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like how you adapted our UI to look more like the design Jingya made:)

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, thanks for doing this!

Copy link

@wujy28 wujy28 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice and clean implementation! LGTM!

@@ -3,17 +3,48 @@
}

#copyButton {
-fx-background-color: dimgray;
-fx-background-color: #3C4EEF;
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, thanks for doing this!

* to ensure that the record being added or updated is
* unique in terms of identity in the UniqueRecordList.
*/
public class UniqueRecordList implements Iterable<Record> {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Neat way to store all the records in the system!

@wujy28 wujy28 merged commit af5f076 into AY2324S1-CS2103T-T14-2:master Oct 27, 2023
0 of 3 checks passed
Copy link

@RiyaMehta2211 RiyaMehta2211 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall. Like how you added snippets of code to make explanation clearer in the DG. Would be good to remove some bits of dead code in the classes edited to improve code readability

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants