Skip to content

Commit 3dd0ccd

Browse files
Merge pull request nus-cs2103-AY2122S1#80 from AY2122S1-CS2103T-T17-3/benedictchuajj-update-UserGuide
Update UserGuide (again)
2 parents e0d25b9 + 2b07eb4 commit 3dd0ccd

3 files changed

Lines changed: 38 additions & 34 deletions

File tree

docs/UserGuide.md

Lines changed: 36 additions & 32 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Finding your next lead has never been easier.
1212
* [Quick Start](#quick-start)
1313
* [Client Information](#client-information)
1414
* [Features](#features)
15-
* [Create new contact: add](#create-new-contact--create)
15+
* [Create new contact: add](#create-new-contact--add)
1616
* [Retrieve particular contact: view](#retrieve-particular-contact--view)
1717
* [Update existing contact: edit](#update-existing-contact--edit)
1818
* [Delete particular contact: delete](#delete-particular-contact--delete)
@@ -82,38 +82,42 @@ Address | String | a/
8282
<div markdown="block" class="alert alert-info">
8383

8484
**:information_source: Notes about the command format:**<br>
85-
86-
* In the format for the commands provided, words which are in UPPERCASE refers to input that the user must key in
85+
86+
* When `<attribute>` is given, it means that the any *attribute tag* can be used, with the exception of *client id* in some cases
87+
88+
* In the format for the commands provided, words which are in `UPPERCASE` refers to the `input` that the user must key in
89+
90+
* If the inputs are wrapped in curly brackets `{}`, they are inputs that are related to the preceeding argument tag
8791

8892
* Inputs in square brackets are optional input:<br>
8993
e.g. `KEYWORD [OTHER_KEYWORD]` can be in the form of `firstName` or `firstName lastName`
9094

91-
* Inputs with ``​ at the end refers to inputs that can be used multiple times in that command
92-
.<br>
93-
e.g. `[tag/ATTRIBUTE]…​` can be in the form of `e/@gmail.com` or `e/@gmail.com r/5`
95+
* Inputs with ``​ at the end refers to commands that can accept multiple attribute inputs
96+
<br>
97+
e.g. `<email>/{EMAIL}…​` can be in the form of `e/@gmail.com` or `e/@gmail.com r/5`
9498
</div>
9599

96100

97101
### Create New Contact : `add`
98102

99103
Adds a new client to the address book.
100104

101-
Format: `add {client’s name} <email>/{email} <phone-no>/{phone number} <risk-appetite>/{risk appetite}...​`
105+
Format: `add <name>/{CLIENT'S NAME} <email>/{EMAIL} <attribute>/{OTHER ATTRIBUTES} ...​`
102106

103107
* A client must have minimally the name and email tag filled during creation
104108
* Any other tags are optional
105109
* Tags that can be added are as seen in the client information in the Client Info Section
106110

107111
Examples:
108-
* `add Benedict Chua e/benchua@hotmail.com`
109-
* `add Keith e/keithtan@ymail.com p/12345678 r/4`
112+
* `add n/Benedict Chua e/benchua@hotmail.com`
113+
* `add n/Keith e/keithtan@ymail.com p/12345678 r/4`
110114

111115

112116
### Retrieve Particular Contact : `view`
113117

114-
View a particular client on your address book to view the client’s information.
118+
Fully view a client’s information in detail.
115119

116-
Format: `view {client’s id number}`
120+
Format: `view {CLIENT'S ID}`
117121

118122
Example: `view 2` would be used to view client 2's information
119123

@@ -124,7 +128,7 @@ attributes of a client, using the tag of the client’s attribute.
124128

125129
* Multiple attributes could be changed with one command.
126130

127-
Format: `update {Client’s id number} <attribute>/{changed value of attribute} ...`
131+
Format: `update {CLIENT'S ID} <attribute>/{CHANGED VALUE OF ATTRIBUTE} ...`
128132

129133
Examples:
130134

@@ -134,9 +138,10 @@ Examples:
134138

135139
### Delete particular contact : `delete`
136140

137-
Deletes an existing client from the address book using any specified attribute to identify the client.
141+
Deletes an existing client from the address book using their either client id or email address identify the client.
142+
Both attributes can be given together.
138143

139-
Format: `delete <attribute>/{value}`
144+
Format: `delete <client id>/{CLIENT'S ID} <email>/{EMAIL}`
140145

141146
* Attributes would be limited to client id, email or both.
142147

@@ -147,7 +152,7 @@ Examples:
147152

148153
### List all contacts : `list`
149154

150-
Shows a list of all tasks in the list.
155+
Shows the full list of all clients in the address book.
151156

152157
Format: `list`
153158

@@ -169,12 +174,12 @@ Examples:
169174

170175
Finds clients whose contacts match with the given keywords.
171176

172-
Format: `search KEYWORD [MORE_KEYWORDS]... [ATTRIBUTE/ATTRIBUTE_KEYWORD]...`
177+
Format: `search [KEYWORD]... [<attribute>/{ATTRIBUTE_KEYWORD}]...`
173178

174-
* `KEYWORD` and `MORE_KEYWORDS` will be used to match will all attribute of the person.
175-
* `ATTRIBUTE/` refers to the argument tag for the client's attribute.
176-
* `ATTRIBUTE_KEYWORD` refers to the keyword that is to be matched with the corresponding client attribute.
177-
* If no `KEYWORD` is provided, search will be based on `ATTRIBUTE/ATTRIBUTE_KEYWORD` only.
179+
* `KEYWORD` will be used to match with all attribute of the person.
180+
* `<attribute>/` refers to the argument tag for the client's attribute.
181+
* `{ATTRIBUTE_KEYWORD}` refers to the keyword that is to be matched with the corresponding client attribute.
182+
* If no `KEYWORD` is provided, search will be based on `<attribute>/{ATTRIBUTE_KEYWORD}` only.
178183
* The search is case-insensitive. e.g `keith` will match `Keith`.
179184
* The order of the keywords does not matter. e.g. `John Doe` will match `Doe John`.
180185
* Clients matching at least one keyword will be returned (i.e. `OR` search).
@@ -190,13 +195,13 @@ Examples:
190195

191196
Filter the current list by the given keywords.
192197

193-
Format: `filter [KEYWORD]... [ATTRIBUTE/ATTRIBUTE_KEYWORD]...`
198+
Format: `filter [KEYWORD]... [<attribute>/{ATTRIBUTE_KEYWORD}]...`
194199

195200
* Works similar to `search` but `filter` works based on the current list shown as opposed to entire lists of contacts.
196-
* `KEYWORD` will be used to match will all attribute of the person.
197-
* If no `KEYWORD` is provided, then filter will be based on `ATTRIBUTE/ATTRIBUTE_KEYWORDS`
198-
* `ATTRIBUTE/` refers to the argument tag for the client's attribute.
199-
* `ATTRIBUTE_KEYWORD` refers to the keyword that is to be matched with the corresponding client attribute.
201+
* `KEYWORD` will be used to match with all attribute of the person.
202+
* If no `KEYWORD` is provided, then filter will be based on `<attribute>/{ATTRIBUTE_KEYWORD}`
203+
* `<attribute>/` refers to the argument tag for the client's attribute.
204+
* `{ATTRIBUTE_KEYWORD}` refers to the keyword that is to be matched with the corresponding client attribute.
200205
* The filter is case-insensitive. e.g `keith` will match `Keith`.
201206
* The order of the keywords does not matter. e.g. `John Doe` will match `Doe John`.
202207
* Clients matching at least one keyword will be returned (i.e. `OR` filter).
@@ -245,13 +250,12 @@ If your changes to the data file makes its format invalid, AddressBook will disc
245250

246251
Action | Format | Examples
247252
--------|---------|---------
248-
**Create** | `add {client’s name} <email>/{email} <phone-no>/{phone number} <risk-appetite>/{risk appetite}`| add benedict e/benedict@gmail.com p/90909898 r/3 |
249-
**View** | `view {client’s id number}` | view 123 |
250-
**Delete** | `delete <attribute>/{value}` | delete i/4 |
251-
**Edit** | `update {Client’s id number} <attribute>/{change value of attribute}` | update 1234 n/Dominic p/12345678 |
253+
**Create** | `add <name>/{CLIENT'S NAME} <email>/{EMAIL} <phone-no>/{PHONE NUMBER} <risk-appetite>/{RISK-APPETITE} ...`| add n/benedict e/benedict@gmail.com p/90909898 r/3 |
254+
**View** | `view {CLIENT'S ID}` | view 123 |
255+
**Delete** | `delete <client id>/{CLIENT'S ID} <email>/{EMAIL}` | delete i/4 |
256+
**Edit** | `update {CLIENT'S ID} <attribute>/{CHANGED VALUE OF ATTRIBUTE} ...` | update 1234 n/Dominic p/12345678 |
252257
**List** | `list` | - |
253-
**Find** | `find KEYWORD [OTHER_KEYWORD]` | find alex tom |
254-
**Search** | `search [KEYWORD]... [ATTRIBUTE/ATTRIBUTE_KEYWORD]...` | search * e/doe@gmail.com r/5 |
255-
**Filter** | `filter KEYWORD [OTHER_KEYWORD] [ATTRIBUTE/ATTRIBUTE_KEYWORD]...` | search * e/doe@gmail.com p/9 |
258+
**Search** | `search [KEYWORD]... [<attribute>/{ATTRIBUTE_KEYWORD}]...` | search * e/doe@gmail.com r/5 |
259+
**Filter** | `filter [KEYWORD]... [<attribute>/{ATTRIBUTE_KEYWORD}]...` | filter * e/doe@gmail.com p/9 |
256260
**Sort** | `sort <attribute>/{ASC/DESC}` | sort r/asc |
257261
**Exit** | `exit` | - |

src/main/java/seedu/address/logic/commands/FilterCommand.java

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ public class FilterCommand extends Command {
1212

1313
public static final String MESSAGE_USAGE = COMMAND_WORD + ": Filter the currently displayed list of persons by"
1414
+ "the specified keywords (case-insensitive) and displays them as a list with index numbers.\n"
15-
+ "Parameters: KEYWORD [MORE_KEYWORDS]...\n"
15+
+ "Parameters: [KEYWORD]... [ATTRIBUTE/ATTRIBUTE_KEYWORDS]...\n"
1616
+ "Example: " + COMMAND_WORD + "e/example.com";
1717

1818
private final PersonContainsKeywordsPredicate predicate;

src/main/java/seedu/address/logic/commands/SearchCommand.java

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ public class SearchCommand extends Command {
1212

1313
public static final String MESSAGE_USAGE = COMMAND_WORD + ": Search all persons whose names contain any of "
1414
+ "the specified keywords (case-insensitive) and displays them as a list with index numbers.\n"
15-
+ "Parameters: KEYWORD [MORE_KEYWORDS]... [ATTRIBUTE/ATTRIBUTE_KEYWORDS]...\n"
15+
+ "Parameters: [KEYWORD]... [ATTRIBUTE/ATTRIBUTE_KEYWORDS]...\n"
1616
+ "Example: " + COMMAND_WORD + " alice bob charlie a/Blk 40";
1717

1818
private final PersonContainsKeywordsPredicate predicate;

0 commit comments

Comments
 (0)