Now the checkstyle is fixed.

Lets adhere to checkstyle.

Now tests should pass on gradle checks.

Lets help gradle pass.

Now code adheres to checkstyle.

lets adhere to checkstyle.

Currently, the name accepts alphanumerical characters, spaces, and
forward slashes. This will allow the majority of names to be added
into the app.

However, it has come to light that there are names which would contain
other characters that would throw errors if users attempt to add these
names in, which is problematic since some special characters like `.`
and `,` are common.

Let's allow several other characters in the regex for names.

In doing so, we can ensure that most common names will be successfully
added into the application.

Fix: remove pop up window for help command

Bug fix: Update name param to include more characters

Update UG for help command

Now version is updated

Lets update version.

Build: update version number

* 'master' of https://github.com/AY2324S2-CS2103T-T10-1/tp:
  Build: update version number
  Update image for help command
  Update chars accepted by Name
  Fix: checkstyle
  Fix: headless environment for gradle
  Style: fix checkstyle
  Fix: remove pop up window for help command

* master: (34 commits)
  Build: update version number
  Update image for help command
  Update chars accepted by Name
  Fix: checkstyle
  Fix: headless environment for gradle
  Style: fix checkstyle
  Fix: remove pop up window for help command
  Fix naming in javaDoc
  Fix spelling errors
  Small changes to test cases
  Comprehensive testing for `CsvUtil` and `ImportCommand`
  Replace references of AB3 with AA
  CsvUtil now throws an IOException for the case when a file is not found in the system
  Update examples to match images
  Update images to match success msg
  Fix: remove magic literal in unit test for import
  Fix: typos in success messages
  Satisfy github CI
  Satisfy Github CI
  Satisfy github CI actions
  ...

fix: add page breaks to ensure good formatting of printed user guide

…into branch_UpdateDeveloperGuide2.0

Currently, the find command holds a predicate, and creates another
predicate based on whether exam scores are needed.

However, this may be messy due to the fact that the predicate
objects are created in different places despite serving the same
purpose.

Let's refactor the creation of the predicate objects to ensure
that the objects follow a more logical and organized flow.

In doing so, the code is both more readable and scalable.

Currently, the application throws a NullPointerException when items in the Exam List and the Person List are clicked on in the User Interface.
This is due to bad implementation practices, as I had put a band aid on this problem by setting the selectionModel of both lists to null to prevent the selection of exams in the list..
While this implementation does not affect the use of the application, Lets update the implementation to use a proper "NoSelectionModel".
This will prevent further NullPointerExceptions from being thrown in the application.

Currently, we were able to observe from the PE dry run that there is
a possibility for testers to perceive from the UG and the error
messages that there may be bugs present despite the code working as
intended.

This is an issue because it indicates that the documentation is not
clear enough to convey the exact reason behind the current behavior of
the code (e.g. semicolons after each copied email after using the
`copy` command, "seemingly valid" emails being rejected).

Let's ramp up the clarity in both the UG and constraint messages
pertaining emails.

In doing so, future users will have a much clearer idea of how the code
is supposed to behave, and will not mistake correct behaviors as bugs.

Now import Command properly displays its Usage message, with
a whitespace between import and i|

ImportCommandParser now also checks for invalid characters in
filePath which is already caught by the InvalidPathException in
java

Currently the readCsv method in CsvUtil only checks if the values
are empty but not if the rows themselves are empty

Currently, as the testers from the PE-D have pointed out, the UG has
room for improvement in regards to the clarity of some of the commands
as well as the omission of usage information for some prefix.

This has to be fixed because future users would likely be unclear in
the purpose behind some of the features of the application.

Let's revamp the UG to include the missing use cases and improve the
clarity of the user guide.

In doing so, future users will have a better idea of the expected
behavior of the app and the rationale of why the behavior of the app
was designed as such.

Now the error messages are more fine tuned with some functionality
changes to provide a more comprehensive and correct message on why
the command is failing.

Lets improve functionality.

Now exam names and names of 1 character length are allowed as long
as they are not blank.

Lets reduce bugs

fix: typo in user guide

fix: Update Ui Image

fix: Additional PE-D UG improvements

Currently, the code does its argument checks with its own code.
However, in built code is already present that achieves the same thing.
Essentially, the typed out code in the findCommandParser is achieving
something that has been coded out already.

To maintain a good coding standard, we should reuse
functionalities already present to avoid repeated code.

Let's implement pre-coded functions in the findCommandParser.

Through this refactor, we can ensure a high coding standard.

Currently, the UG has very minor spelling errors.

We need to fix this because it undermines the professionalism of
the UG.

Let's fix these typos.

In doing so, we uphold a higher level of professionalism.

Update Developer Guide with new Logic, UI, Model and Storage implementations

fix: Clarify email and copy related docs and messages

Bug fixes for PE-D

Fix ped bugs: Leng Khai

Bug fix: Refactor Find Functionality

For the case of duplicate headers, there is a bug in which when
there are 2 email coloumns with the same value, the person is not
added to the addressBook. (As stated in the PE-D, issue #362).

This is fixed by now correctly ignoring the duplicate column

The present developer guide is lacking in documentation for our newly implemented exam features.
Lets update the developer guide with explainations and diagrams detailing our exam features so
that potential developers may build upon our application easily.

* 'master' of https://github.com/AY2324S2-CS2103T-T10-1/tp: (22 commits)
  Fix minor typos
  Fix Spelling
  Refactor find functionality further
  Update UI Diagram
  Fix: length constraints of fields
  Fix: Correct ImportExamScores command
  UG improvements
  Update Logic with specific details
  Clarify email and copy related docs and messages
  Fix NullPointerException when clicking UI
  Update error messages to match correct usage
  Update Storage Load Sequence Diagram
  Update Storage component in DG
  Update Ui Image
  Refactor Find Functionality
  Update UI and Model in DG
  fix: typo in user guide
  Update Ui DG description
  Update Model and Ui in DG
  fix: add page breaks to ensure good formatting of printed user guide
  ...

* master: (211 commits)
  Fix minor typos
  Fix Spelling
  Refactor find functionality further
  Update UI Diagram
  Fix: length constraints of fields
  Fix: Correct ImportExamScores command
  UG improvements
  Update Logic with specific details
  Clarify email and copy related docs and messages
  Fix NullPointerException when clicking UI
  Update error messages to match correct usage
  Update Storage Load Sequence Diagram
  Update Storage component in DG
  Update Ui Image
  Refactor Find Functionality
  Update UI and Model in DG
  fix: typo in user guide
  Update Ui DG description
  Update Model and Ui in DG
  fix: add page breaks to ensure good formatting of printed user guide
  ...

Now they are correctly labelled as static classes without
multiple instances.

Lets improve documentation

Now the text is easier to read.

Lets improve documentation

Now documentation covers the deleteShown command, so that
developers are aware of the usage and implementation.

Lets improve documentation.

Now the command has details on how it is implemented for the
consideration of developers.

Lets improve documentation.

Now the activity diagram clearly shows the flow of parsing
a filepath as input.

Lets improve documentation

Now the activity diagram illustrates the implementation and process
of the deleteShown command.

Lets improve documentation

Now the headers are more in line with Johan's proposed additions.

Lets enhance consistency.

Now the opencsv library is properly acknowledged in our source
code and documentation.

Lets ensure proper code reuse.

Now the DG covers comprehensively the add feature.

Lets enhance documentation.

Now the DG covers the implementation of the edit command so that
developers can easily refer to and understand it.

Lets improve documentation.

Now the manual testing steps are detailed for add, edit, delete,
deleteshown, list, importExamScores, launch and shutdown are
detailed so that manual testers are clear on how to test them.

Lets improve documentation.

Now manual testing instructions are clearer.

Lets improve documentation.

Now the test is neater.

Lets improve testing

the effort section in the developer guide aims to showcase to viewers
the effort we put into developing avengers assemble.

add,
* difficulty level by explaining the new entity added
* challenges faced by explaining the different considerations we had to
make
* effort required by explaining the features we enhanced and the new
features added into our application

this section is incomplete as it required more inputs from other members
for their though process behind the implementations.

Now the planned enhancements for features we did not have time to
implement are shown in the DG.

Lets improve documentation.

Now the DG covers the planned implementation for a more enhanced
input validation for the find command.

Lets improve documentation

instructions for manual testing allows for consistency on how avengers
assemble is tested across different developers. developers may have
different interpretations on what needs to be tested and how different
features should be tested.

add,
* instructions for manual testing for export command
* instructions for manual testing for addScore command
* instructions for manual testing for editScore command
* instructions for manual testing for deleteScore command
* instructions for manuals testing for mean and median calculation
feature

this needs further discussion and should be agreed upon by everyone in
the team.

Update sequence diagram to include `CsvUtil`

Add manual testing for importing of persons

…into branch-FinaliseUG

# Conflicts:
#	docs/DeveloperGuide.md

Currently, the DG has the user stories relevant only to v1.2, meaning
all exam and score related implementations have been excluded from
the user stories and use cases.

As such, the user stories and use cases are outdated and need to be
refurbished.

Let's update the user stories and use cases to correctly reflect the
current functionality implemented into Avengers Assemble.

By maintaining the user stories and use cases, future developers
will be able to understand the motivation and logic behind the current
suite of features.

Note: this commit also contains minor changes to the UG from feedback
given from the PE-D.

Currently, the manual testing section does not include instructions for
functionalities currently implemented.

We need to keep this updated to allow future developers to check
each functionality manually to ensure the code behaves as intended.

Let's update the Manual Testing instructions to include comprehensive
instructions for the following commands:
* `help`
* `clear`
* `find`
* `copy`
* `exit`

In doing so, these commands can be tested with the assurance that
all aspects of the behaviours of these functions are covered.

Currently, the find command does not check that there are duplicate
prefixes present in the input provided by the user.

This is problematic because it allows the find command to accept
multiple duplicate prefixes despite the command being documented to
only accept one single prefix.

An example is `find n|alice n|bob`
* Expected behaviour: throw an error indicating more than one prefix
is used.
* Actual behaviour: finds persons with names containing bob.

Because this behaviour differs from the user guide, does not handle the
error of duplicate prefixes, and behaves different from normal
expectations, the following error can be classified as a functionality
bug, and not a feature flaw.

Let's rectify this problem by using the in-built duplicate verifier to
properly handle the issue of duplicate prefixes.

Doing so not only solves the bug, but also does so in a way that does
not implement any new functionality into the code.

Now the activity diagrams look consistent and nicer.

Lets improve documentation

Now the activity diagram is specified to represent the workflow to
minimize confusion.

Lets improve documentation

…seCases

docs: update DG to reflect user stories and use cases to reflect all implemented functions

…cate

bug fix: prevent execution of find command with duplicated prefixes present

add,
* implementation details for addScore, editScore, deleteScore

sequence and activity diagrams have not been added in.

guide

remove implementation details section as it is a repeat of all the
content below it.

Docs: Add assigned parts to DG

include more details on the validation of index and score for addScore,
editScore, and deleteScore.

Currently, the DG manual testing section is not organized according to
the order of the UG.

However, we want to maintain a level of standardization that gives
the impression that all documentation was written by one person.

Let's reorder the manual testing section to maintain a standard order.

By keeping the structure standardized, the DG will not only appear more
organized, but it will help the future developers in navigating through
the DG.

Docs: Update Manual Testing Section of DG

BugFix: Bug Fixes from PED