Charisma Kausar's Project Portfolio Page

### 5.3 Delete fields feature
The **delete fields** feature can be used to delete fields stored for the
contacts. This feature is also restricted to the Contact Details Page,
which can be accessed after the _add_ or _view_ commands. It is mainly
facilitated by the `ContactDetailsPageParser`, `DeleteFieldCommandParser`
and `DeleteFieldCommand` classes.

_Note:_ This feature is different from the **delete contacts** feature,
which is only accessible on the Home Page.

#### 5.3.1 Design considerations:
Since certain fields allow for multiple values to be stored, the user needs
to specify the label of the value (or the value itself for non-labelled
fields) they want to delete along with the field to be deleted for such
fields.

**Aspect: What happens when the user does not specify a label or value:**

* **Alternative 1 (current choice):** Delete all the values stored for this
  field immediately.
  * Pros:
    * Seems to be the most intuitive approach.
    * Easier to implement.
    * Faster to execute command.
  * Cons:
    * User may have forgotten to mention the label or field, which could
      lead to unintended loss of data.

* **Alternative 2 :** Confirm that the user wants to delete all values for
  this field
  * Pros:
    * Allows user to cancel the command if it was unintentional.
  * Cons:
    * Slower to execute command.
    * Difficult to implement, since the current implementation does not
      store command history.

We picked _alternative 1_ since the focus of our CLI app is on speed and
efficiency. Additionally, _alternative 2_ required a lot of changes to the
existing implementation which would not be very helpful for executing other
commands.

### 5.4 Clear all data feature
The **clear all data** feature can be used to delete all the contacts
and meetings stored by the user. Since deleted data cannot be recovered,
the app opens a pop-up window asking for user confirmation before any
data is cleared.

The following sequence diagram shows how the clear operation works:

![ClearSequenceDiagram](/tp/images/ClearSequenceDiagram.png)

This activity diagram summarises the possible paths of executing the _clear_
command:

![ClearActivityDiagram](/tp/images/ClearActivityDiagram.png)

### 8.4 Deleting fields
1. Deleting only particular fields of a contact

  1. Prerequisites: Have at least one contact stored with multiple phone
     numbers, tags, pronouns and the job title and view their details with
     the `view <INDEX NO>` command. These test cases must be followed in
     order.

  2. Test case: `del` <br>
     Expected: No field is deleted. An error message is shown in the Result
     Display.

  3. Test case: `del ph` <br>
     Expected: No field is deleted. An error message is shown in the Result
     Display.

  4. Test case: `del ph/ <LABEL OF FIRST PHONE NUMBER>` <br>
     Expected: The first phone number is deleted while the rest are still
     displayed in the contact details.

  5. Test case: `del t/` <br>
     Expected: All the tags of the person displayed are deleted. <br>
     Exception: If there is another contact with the same name as this
     contact but without any tags, this command will result in an error
     and no fields will be deleted.

  6. Test case: `del pr/ j/` <br>
     Expected: All the pronouns and the job title of the person displayed
     are deleted.

  7. Test case: `del j/` <br>
     Expected: No field is deleted. An error message is shown in the Result
     Display.

#### 3.3.1 Creating a meeting: `meet`
Create a meeting by specifying the following information:
- Agenda
- Meeting place
- Meeting date and time: in DD-MM-YYYY HH:mm format
- Attendees: in the form of index numbers of people on the displayed list

_Note:_ All fields are compulsory.

Format: `meet for/<AGENDA> in/<MEETING PLACE> on/<MEETING DATE AND TIME> 
with/<ATTENDEE 1 INDEX> [<ATTENDEE 2 INDEX>]…`

Example: `meet for/Project Discussion in/UTown on/28-04-2022 13:30 with/1 3 4`

#### 3.3.2 Updating meeting details: `update`
Update any of the meeting’s details by indicating the following:
- Meeting index: The index of the meeting you want to edit on the meetings 
  list
- Any of the meeting details given under 
  [6. Meeting Fields Summary](#6-meeting-fields-summary).

Format: `update <MEETING INDEX> [in/<MEETING PLACE> on/<MEETING DATE AND 
TIME> with/<ATTENDEE 1 INDEX>...]`

Example: `update 2 in/COM2 on/29-04-2022 20:00`

#### 3.3.3 Canceling a meeting: `cancel`
Cancel a meeting by specifying its index on the meetings list.

Format: `cancel <MEETING INDEX>`

Example: `cancel 2`

#### 3.3.4 Canceling all meetings: `cancel-all`
Clear your meetings list by canceling all meetings.

Format: `cancel-all`

<div markdown="span" class="alert alert-warning">:exclamation: **Caution:**
This action is irreversible.
</div>