Update UG and DG #183
Update UG and DG #183
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
|
|
||
| Format: `search t/TAGNAME...` | ||
| Prefix | Constraints |
There was a problem hiding this comment.
Consider adding type (mandatory/optional) column? Can consider doing a merged column filled with mandatory*
There was a problem hiding this comment.
Regarding this part, technically all fields are optional, but they need at least 1 of the "optional" fields. But I wasn't sure how to word this without making it even more confusing (as flagged by Jun Hiang during our UG consult) so I just got rid of the mandatory/optional column. Any suggestions on how to solve this?
There was a problem hiding this comment.
I simply added Mandatory* and added a clarifying note below it for delete. You can refer to image below.
| e.g. `search n/Alex n/Adam st/rejected` is not allowed. | ||
| <box type="tip" seamless> | ||
| Tip: | ||
| * You can combine multiple search categories in a single `search` command. |
| Examples of successful command execution: | ||
| 1. `search n/alex bernice` | ||
| <br> | ||
|  |
There was a problem hiding this comment.
Not sure why but picture doesn't show up
| What does it mean to do an `OR` search within a single category and an `AND` search across multiple categories? | ||
| It's best to explain this by breaking down an example `search` command! | ||
| `search n/alex bernice st/interviewed t/intern` will output applicants whose: | ||
| * names contain either Alex `OR` Bernice |
Changes to UG:
searchandcreateChanges to DG:
modelandstorageclass diagrams