Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CS2113-F11-3] TourPlanner #42

Open
wants to merge 453 commits into
base: master
Choose a base branch
from

Conversation

Bobowoo2468
Copy link

@Bobowoo2468 Bobowoo2468 commented Oct 1, 2021

TourPlanner is a desktop application meant for employees of travel agencies. Its main purpose is to manage clients, flights, accommodations and trip packages data, optimized for use via a Command Line Interface (CLI). If you can type fast, this application can allow one to access relevant travel information faster than traditional GUI applications.

Bobowoo2468 and others added 21 commits October 24, 2021 23:02
Re-organised the classes, placed them in respective folders.
For clients, sort by Id and name, in alphabetical order.

For tours, sort by TourCode and price, in ascending and alphabetical order respectively.
# Conflicts:
#	src/main/java/seedu/duke/Ui.java
#	src/main/java/seedu/duke/commands/tours/SortTourCommand.java
Add sort functionality for Clients and Tours
…cut class of Client, Tour, Flight and Package classes
# Conflicts:
#	src/main/java/seedu/duke/CutClientCommand.java
#	src/main/java/seedu/duke/Parser.java
#	src/main/java/seedu/duke/SortTourCommand.java
#	src/main/java/seedu/duke/TourList.java
#	src/main/java/seedu/duke/Ui.java
Add clientPackageId attribute to ClientPackage class, add and update cut class of Client, Tour, Flight and Package classes
� Conflicts:
�	src/main/java/seedu/duke/Parser.java
�	src/test/java/seedu/duke/ParserTest.java
Add sort flights functionality
# Conflicts:
#	src/main/java/seedu/duke/Parser.java
Copy link

@irvinseet irvinseet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No visuals used e.g., screenshots/diagrams. Although architecture diagram is optional, I think it is good to include as it gives readers and overview of your code.

Comment on lines 12 to 17
The add feature is facilitated mainly by `Parser`, and returns an `AddCommand` object. When `AddCommand` is executed,
the values corresponding to their fields are added.

After receiving the command from the user by `readCommand` of `Ui`, the command is parsed by `Parser`. The `Parser`
first determines the command type by separating the command from the subsequent arguments. After determining the
command, `Parser` executes the specific methods to sense-make the arguments, in response to the specific command.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You want want to add a diagram here showing the interaction between UI and Parser

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe can also include an over-arching software architecture diagram to show how the high-level components connect.


The following activity diagram summarizes the following steps.

![image](yuemel.png)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image not showing on github pages

Comment on lines 156 to 158
* Alternative: only iterate through the ```Package``` List.
* Pros: fast querying time.
* Cons: If the client has not subscribed to a package, none of their information can be accessed, including their contact number.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Formatting seems abit off here. Is this "Alternative" a standalone point. If yes, you may want to remove the bullet point for the first line


<br>

### <u>Design Considerations</u>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does "design consideration" belong to "Finding a particular client". If so, please under different font sizes to indicate it is a subheading

Comment on lines 23 to 26
* `add -c NAME /cn 91234567`
* `add -t JPN /n Hokkaido-A /p 1500`
* `add -f SQ-JPN /t JPN /f SG dt 20-10-2021 18:00 /df 21-10-2021 03:00`
* `add -p ID /c NAME /t JPN /f SQ-JPN`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps can add the English equivalents of these commands

Comment on lines 33 to 35
```
-t JPN /n Hokkaido-A /p 1500 --> -t <<split>> JPN /n Hokkaido-A /p 1500 --> [-t, JPN /n Hokkaido-A /p 1500]
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For all the steps, you may want to separate and colour code the different attributes, then the splitting will be more visual and obvious to the reader.

e.g. /n Hokkaido-a (#red) /p 1500 (#blue) --> /n Hokkaido-a (#red) <> /p 1500 (#blue)

* ```FindClientCommand(String name)```

* ```FindTourCommand(String code)```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Inconsistent format for classes

Bobowoo2468 and others added 30 commits November 8, 2021 18:53
…into Wayne-v2.1

# Conflicts:
#	src/main/java/seedu/duke/Ui.java
Add major bugfix to addCommand
Fix clientPackageCommand bug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants