From 39071ef93c40dc25a87091b2e0fe0d21edd4f5e0 Mon Sep 17 00:00:00 2001 From: Rachel Date: Mon, 11 Nov 2024 12:16:47 +0800 Subject: [PATCH] Revert "Add notes on how email and dates are parsed" --- docs/UserGuide.md | 35 +++++++++-------------------------- 1 file changed, 9 insertions(+), 26 deletions(-) diff --git a/docs/UserGuide.md b/docs/UserGuide.md index bb02508fe42..3d92e44305b 100644 --- a/docs/UserGuide.md +++ b/docs/UserGuide.md @@ -320,7 +320,7 @@ A **person** is a patient with several fields. The fields and their correspondin |------------------|--------|----------|----------|--------------------------------------------------------| | **Name** | `n/` | No | No | Only alphanumeric characters (Cannot start with space) | | **Phone number** | `p/` | No | No | Positive integer of length 3-15 (Inclusive) | -| **Email** | `e/` | No | No | Refer to 1. below | +| **Email** | `e/` | No | No | Refer to * | | **Address** | `a/` | No | No | Any value | | **Status** | `st/` | No | No | Only alphanumeric characters | | **Tag(s)** | `t/` | Yes | Yes | Only alphanumeric characters | @@ -328,9 +328,7 @@ A **person** is a patient with several fields. The fields and their correspondin You can identify these patients uniquely by their **patient ID (PID)** for easy reference. --- -**Notes** - -1. Emails must have a local part containing alphanumeric characters and specific symbols (`+_.-`) (not at the start or end), followed by `@`, and a domain part with labels separated by periods, ending in a label with at least two alphanumeric characters, and no labels starting or ending with hyphens. +* Emails must have a local part containing alphanumeric characters and specific symbols (`+_.-`) (not at the start or end), followed by `@`, and a domain part with labels separated by periods, ending in a label with at least two alphanumeric characters, and no labels starting or ending with hyphens.
@@ -423,13 +421,6 @@ Edits an existing patient in DocTrack. - - -**Note:** When editing the name of a person, the person's appointments will not reflect the name change until a reload -of the application. - - - **Navigate back to the subsections here:** @@ -547,20 +538,16 @@ Note that this will also clear the appointment data. An **appointment** is defined by several fields. The fields and their corresponding prefixes are as follows: -| Field | Prefix | Optional | Multiple | Acceptable Inputs | -|---------------------|--------|----------|----------|---------------------------------------| -| **Person ID** | `i/` | No | No | Existing person ID | -| **Appointment Type**| `ty/` | No | No | Any value | -| **Date and Time** | `d/` | No | No | `yyyy-MM-dd HH:mm`. Refer to 1. below | -| **Sickness** | `s/` | Yes | No | At least one alphabetic character | -| **Medicine** | `m/` | Yes | No | At least one alphabetic character | +| Field | Prefix | Optional | Multiple | Acceptable Inputs | +|---------------------|--------|----------|----------|-----------------------------------| +| **Person ID** | `i/` | No | No | Existing person ID | +| **Appointment Type**| `ty/` | No | No | Any value | +| **Date and Time** | `d/` | No | No | `yyyy-MM-dd HH:mm` | +| **Sickness** | `s/` | Yes | No | At least one alphabetic character | +| **Medicine** | `m/` | Yes | No | At least one alphabetic character | You can manage the appointments through different commands, which can be seen in the table below: -**Notes:** - -1. The date and time inputs are resolved "smartly" - meaning that certain incorrect dates will be allowed, e.g. `2025-02-29 12:00` will be parsed as `2024-02-28 12:00`. -
| Action | Format | Examples | @@ -647,8 +634,6 @@ You can an existing appointment in appointment book.
-
- **Navigate back to the subsections here:** @@ -965,5 +950,3 @@ folder, you can copy these files to another location as a backup. 3. On **MacOS systems**, the bold fonts may appear slightly clipped.
- -4. Editing the name in the `edit person` command will not reflect the name change in the appointments until a reload of the application.