Update DG for query related commands #218
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Alteqa
requested changes
Apr 12, 2024
docs/DeveloperGuide.md
Outdated
|
|
||
| Queries a 'doctor' or 'patient' entry by indicating their name or a substring of their name. | ||
| This command is implemented through the `QueryDoctor` and `QueryPatient` classes which extend the `Command` class. | ||
| * Step 1. User enters an `find` command. |
docs/DeveloperGuide.md
Outdated
| This command is implemented through the `QueryDoctor` and `QueryPatient` classes which extend the `Command` class. | ||
| * Step 1. User enters an `find` command. | ||
| * Step 2. The `AddressBookParser` will call `parseCommand` on the user's input string and return an instance of `findCommandParser`. | ||
| * Step 3. The `parse` command in `FindCommandParser` calls `ParserUtil` to create instances of objects for each of the parameters. |
There was a problem hiding this comment.
theres no parseutil in the find command parse method
docs/DeveloperGuide.md
Outdated
| * Step 6. The `execute` method in `FindCommand` executes and calls `updateFilteredPersonList` in model with the `NameContainsKeywordsPredicate` to get a filtered list of person entries of the entered keyword(s), both `patient` and `doctor` entries can be displayed. | ||
| * Step 7. A Success message gets printed onto the results display to notify user and the list of matching results is produced. | ||
|
|
||
| The sequence diagram below closely describes the interaction between the various components during the execution of the `DeleteAppointmentCommand`. |
There was a problem hiding this comment.
Findappointment not delete
docs/DeveloperGuide.md
Outdated
|
|
||
| * Step 1. User enters a `doctor` command. | ||
| * Step 2. The `AddressBookParser` will call `parseCommand` on the user's input string and return an instance of `QueryDoctorCommandParser`. | ||
| * Step 3. The `parse` command in `QueryDoctorCommandParser` calls `ParserUtil` to create instances of objects for each of the fields. |
There was a problem hiding this comment.
im not sure if querydoctorcommand parser calls parserutil
docs/DeveloperGuide.md
Outdated
|
|
||
| * Step 1. User enters a `patient` command. | ||
| * Step 2. The `AddressBookParser` will call `parseCommand` on the user's input string and return an instance of `QueryPatientCommandParser`. | ||
| * Step 3. The `parse` command in `QueryPatientCommandParser` calls `ParserUtil` to create instances of objects for each of the fields. |
There was a problem hiding this comment.
again not sure if it calls parserutil
Alteqa
approved these changes
Apr 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
find
patient
doctor
apptforpatient
apptfordoctor