Create view command

Modify Delete Command to use IC Number

Currently, the deletecommand is finding a patient to delete based
on a filtered list rather than full list of patients

It is important for a user to delete a patient outside of the
filtered list as well.

Create a getCurrentPatientList method in ModelManager.java to
get the current list of patients

Make changes to edit and delete to access a patient in the list using ic number instead of patient index. Update User Guide to reflect these changes to edit and delete commands.

Let's modify User Guide to ensure an easy tutorial for the users

Currently, the Add Command is implemented in a way that patients
with similar ic numbers are allowed to be added

Since ic numbers should be unique to every patient, it is important
to inform users that the ic number of the new patient already exist

Update AddCommand.java and AddCommandTest.java for ic number check

Update project from team repo

Currently the UI Component section of the developer guide
is outdated and missing information related to the
newly added RecordCard and RecordPanel classes.

Updating the guide can help us keep better documentation
of our project.

Let's add the newly added RecordPanel and RecordCard
classes to the UML diagram and alter the explanation
to include them as well.

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.

Implement Record command to edit patient record.

A Record attribute with relevant fields has been created for our Patient
class. However, it cannot be edited and will stay as default values.

Implementing a record function will allow us to take the first step in making
a more viable product with suitable features.

Let’s create the RecordCommand classes along with parser and test
classes. Doing so will allow us to edit a patient’s record more efficiently.

Fix Checkstyle Errors

Some classes have errors with checkstyle.

Fixing the checkstyle errors will ensure that the errors do not
accumulate.

Let’s make sure we run checkstyle before pushing our code.
Doing so will allow us to have cleaner code.

Modify User Guide to include Edit and Delete Features

Add Birthday class and save Assigned Department to Storage. Also modify delete and edit a patient to use IC Number instead of index of the patient.

Currently, the app does not support the editing of department
or the assignment of a patient to a department.

This functionality must be added for our app to be fully
functional as per its functional requirements.

Let's,
* Add an AssignCommand class to handle the command execution
* Add an AssignCommandParser class to parse user input
* Add the command to the AddressBookParser

The current developer guide lacks details regarding our
new features.

Updating it now would alleviate the burden of having
to do them later.

Let's add a section about how our department attribute
and assign department feature is implemented.

Modify DeveloperGuide.md to include enhancements

Update DG with Implementation of Record Command

A New Record Command has been created and implemented. DG does
not contain information about the Record Command.

Updating the DG will ensure that DG is kept up to date and fellow
developers understand the implementation of the newly added Record command.

Let’s keep the DG up to date with our enhancements. Doing so allows
everyone to be aware of the changes made and how they were made.

Update Add command to check for existing Ic Number

Currently there is placeholder text for the sequence diagram
for assign department in the implementation section.

Let's replace it with the actual diagram.

Update DG with Record Feature

Update DG with Assign Department Feature and Ui Component

Add `Record` JSON Storage Format to DG

Implement Record Command

Add Assign Department Functionality to App

…t Command

Fix Bug of Assigned Department and Record being reset after using Edit
Command

Assign and Record Commands have been created to edit assigned
department and record. Using the Edit Command will reset the edited
assigned department and record back to default.

Fixing this bug will ensure that all relevant fields are kept even after
modifying their values.

Let’s add a Patient Constructor that takes in both the assigned
department and record. Doing so allows us to keep the assigned
department and record values even after using the edit command.

Fix Checkstyle Errors

Some classes have errors with checkstyle.

Fixing the checkstyle errors will ensure that the errors do not
accumulate.

Let’s make sure we run checkstyle before pushing our code.
Doing so will allow us to have cleaner code that passes checks.

Fix Github Check Errors

Some classes have errors with checkstyle.

Fixing the checkstyle errors will ensure that the errors do not
accumulate.

Let’s make sure we run checkstyle before pushing our code.
Doing so will allow us to have cleaner code that passes checks.

Currently, the edit command requires user input like edit <IC> n/<edit name>... However, this is not consistent with the user inputs for other commands.

Let's change edit command and corresponding edit command tests to take in input like edit i/<ic> n/<edit name> etc.

Create Method to Copy Record Information

The Patient class has a constructor that takes in Record as a
parameter and sets its record field to the Record given in the
parameter. However, this would make a patient have a Record
that could be tied to another Patient.

Creating a method to copy the Record information will ensure that
the Patient field of the Record matches.

Let’s be careful in our code. Doing so will allow our product to be
more future-proof and error-free.

Fix Edit Bug and Checkstyle Errors

Currently, when you edit a patient's details, the GUI
does not update with the new details unless you reselect
the patient in the list.

We must fix this bug so that the user can view the new
details easily.

Let's edit the RecordPanel class to handle the event
when the patient's details changes properly.

Currently, when no argument is given to delete command, it causes an
exception in the system and no help message is shown.

It is important to notify users of any help message when required

Update DeleteCommand.java and DeleteCommandParser.java to fix help
message bug

The record fields in the GUI currently do not update
when the user edits the record using the record
command. There is also the remark field in the GUI
even though we do not intend for the user to edit it.

We should fix the bug and remove the remark so that the
program works like intended.

Let's
* Wrap the Record fields in SimpleStringProperty so that
changes to them can be observed by listeners in the GUI.
* Change the container type of record fields in the GUI
from TextFlow to TextArea.
* Add the GUI components as listeners to the events of the
Record Card fields.
* Remove the remark box from the GUI."

The changes needed for the GUI to update when record
is edited previously involved the refactoring of
String attributes in Record into SimpleStringProperty.

However, such changes in Record were not required for
the bug fix we need for the GUI.

Let's simplify the changes so that we can avoid
modifying what we have previously done as much
as possible.

Currently, the GUI still looks different from the
intended UI.

We should update it to match.

Let's modify the CSS and layout of the UI components
so that they resemble the initial design.

When running the application, there are many warnings about
the wrong JavaFX version that show up in the console.

We should remove these warnings so that the application can
run as smoothly as possible.

Let's fix these warnings and also make some final changes
to the GUI of the application.

Update GUI to look like our final product

Currently, the record feature does not show help message for
no input

It is important to let the user know of any useful help message

Update RecordCommandParser to throw exception with helpful message

Add Priority Attribute

Having priority as an attribute of patients would be helpful for ED
doctors. Our system does not have a Priority attribute.

Creating a class for Priority will ensure that this can be implemented
as part of a Patient.

Let’s create the classes: Priority and PriorityTest. Doing so
will ensure that the user can input important information about patients
into the application and ease subsequent testing of the information.

Currently record command does not test if ic number already exist

It is important to do integration testing for ic number to ensure system
work as expected.

Add RecordCommand testcases testing existing ic number

Currently when no patients with the keyword is found, no error
message is given.

It is important to inform the user with helpful error messages

Update FindCommand and FindCommandTest to handle no patient with
keyword found

Currently, there is no developer guide implementation for
add command.

It is important to update the developer guide to ensure that future
developers can understand our implementation philosophy

Update DeveloperGuide.md to include implementation for add command

Make Edit Command with i/ prefix in user input

Update commands to show error message if field does not exist

Let's modify the Edit Command Parser and the corresponding test cases to parse raw user inputs without the command word

Implement Priority Attribute

Priority attribute has been created for our Patient class. However, it
is not being implemented in our system.

Editing the relevant classes will ensure that the Priority attribute is
implemented and functional.

Let’s edit the Patient, Command and etc. classes to implement
Priority. Doing so will ensure that the Priority attribute can be used
and provide benefits to users.

Make Edit Command Parser with i/ prefix in user input

Add and implement Priority attribute

Fix & Add Test Cases

Some test cases are failing due to our implementation. There is also a
lack of test cases in some areas.

Editing the test cases will ensure that our system is more well-tested.

Let’s fix and add more test cases. Doing so will ensure that failed test
cases do not accumulate.

Fix & Add Test Cases

Currently, the testing for Edit related features like EditCommand and
EditCommandParser are failing.

It is important to ensure that the test cases pass at all times so as
to ensure the workability of that segment of code.

Update EditCommandParserTest.java and EditCommandTest.java to fix
failing test cases

Currently, the Age class is unused.

We want to include the Age attribute in Patient so
that users can view and make use of this information
to make decisions.

Let's,
* Modify the age class to be so that it instantiated
with birthday to support the auto-computation of age
* Add the age attribute to the patient

Currently, there is an issue with the test case for equals()
in Patient. This test case is believed to arise from the
addition of the age.equals into the equals method.

Perhaps removing it will fix the test case failure.

Let's remove the equality checking for age in Patient and
add age into the toString test case expected output."

The statement was removed due to it being suspected to
have caused the test case failure in PatientTest for
the equals method.

However, it appears to not be the cause of the issue,
after checking with other programmers.

Let's add it back into equals for completeness.

Currently, the AgeTest tests and BirthdayTests are
outdated and do not take into account the new changes.

We should update the test cases to ensure that our
tests are testing the updated methods properly.

Let's add new test cases for the constructor and toString
methods in Age, and for the isValidBirthdate method in
BirthdayTest.

Update Edit command related tests

Add auto-computation behavior for Age

Currently, the age is computed with the formula,
age = current year - birth year.

However, this does not consider whether the birthday
has passed for that year, and is different from
how people generally compute their age.

Let's change the implementation to fit our
understanding of age and birthdays.

Currently, there are no test cases for Asssign Command

It is important to ensure all components of the software is
tested to ensure workability.

Create AssignCommandTest.java and AssignCommandParserTest.java

Improve implementation of Age

Currently, there lacks a command for users to sort
the patient list by a given property.

We should add it to allow patients to better
organize their data.

Let's,
* Add the SortCommand and SortCommandParser
classes
* Modify Priority class to store the enum type
as its value instead of a string

Note that the function is currently implemented
such that you can sort the displayed filtered list,
but doing so will also sort the underlying full list.
It is this way as the filteredpatientlist cannot be
modified, so sorting the underlying addressbook is
the fastest and easiest way to add this functionality
without modifying the structure of the model and ui
too much."

Create test for Assign Command feature

Update project

Remove Record attribute from Storage to debug.

Currently, the patient record storage does not support JSON serialization/deserialization for
critical attributes like initial observations, diagnosis, and treatment plan. Additionally,
the UniqueRecordList class lacks comprehensive test cases to validate its behavior.

Enhancing JSON storage will ensure all necessary patient details are persisted, and expanding
test coverage for UniqueRecordList will help maintain data integrity and prevent potential bugs.

Let's,
* Update JsonAdaptedPatient to serialize/deserialize additional patient attributes
* Add extensive test cases for UniqueRecordList to cover various scenarios

The current version of the User Guide lacks a comprehensive introduction,
and the photos within are not displayed at an optimal size.

Let's,
* Enhancing the introductory section with additional details to provide a clearer overview.
* Rescaling the photos in the User Guide to improve readability and visual appeal.

Implement JSON storage for patient records

Improve User Guide Introduction and Adjust Photo Sizes

Priorities are currently not visible to the user
in the GUI.

We should make them visible for easy reference.

Let's,
* Restyle the tags
* Add a priority tag
* Do other small adjustments to make the UI look
better.

Add sort command and UI changes

Currently theres no diagrams for the View feature

It is important to provide diagram to best aid future developers
in using our software.

Create ViewSequenceDiagram.puml

Currently, there is no diagram depicting the control flow of the
Add command.

It is important to provide diagram to best aid future developers
in using our software.

Create AddSequenceDiagram.puml

Some commands like clear can have massive implications if performed wrongly with large databases being lost.

Hence, implemented Undo and Redo to cushion such loss in data. Also added corresponding test cases, updated user guide, and fixed test cases from other classes

Currently the user guide does not have quick start component

It is important to ensure that user guide have this component
so that users will know how to start with our product.

Update UserGuide.md to add quick start component

Add Undo and Redo Command