bchenghi / ped Goto Github PK

There is a typo in the User Guide section 4.2.1, under the "Examples:" section, the 2nd example. Perhaps the pr/MEDMIU should be spelt as pr/MEDIUM? Similar for figure 2 below the example.

I am unable to see the entire attraction description if the description is too long, even in full screen. This can be reproduced by adding an attraction with a very long description or editing an existing one with a long description. Perhaps the number of characters of the description can be limited instead?

The link provided in the User Guide, section 3, point number 6, features does not seem to work as it redirects the user to the start of the User Guide instead of the features section.

The font used for Figure 17's description is smaller than other figures.

The example given in the add-attraction cannot be executed since the attraction already exists in the application. Perhaps for the user to try out, the user can add an attraction that does not exist yet? This can be reproduced by starting the app with the starting data, then adding the example attraction given in section 3.5.

When the attraction name is too long, I am unable to see the entire attraction name even in full screen. This can be reproduced by adding an attraction with a very long name, or editing an existing attraction's name to be a very long one. Perhaps the length of the name can limited to a certain number of characters?

If the location name is too long I am unable to see the entire location name even in full screen. This can reproduced by editing a current attraction's location entry with a very long name, or adding an attraction with a long location name. Perhaps it can be limited to a fixed number of characters.

After creating an Itinerary, and not selecting it, I tried add-itinerary-attraction 1 st/1000 et/1100 day/1. Which showed "This attraction already exists in the itinerary." as the error message although no itinerary was selected. No commands were executed on the itinerary yet, so the itinerary is empty as well.
This can be reproduced by creating a new itinerary, then executing add-itinerary-attraction 1 st/1000 et/1100 day/1.

Documentation did not include conditions for duplicate attraction and itinerary, so the user might not know why he/she is unable to add the an attraction or itinerary. Perhaps the conditions can be specified in a glossary or in the adding or editing command sections in the User-Guide. This can be reproduced by the add-attraction example given in section 3.5 of the User Guide.

For add-itinerary command, I used 32-10-2020 for the start date, but I received "Date should be of the format dd-mm-yyyy" as error message. Perhaps it could be about invalid dates instead? This can be reproduced by add-itinerary n/NAME sd/32-01-2020 ed/01-01-2021

The error message has minor typos. It is missing spaces in the message. This can be reproduced by typing delete-itinerary-attraction after selecting an itinerary. For instance in the last line "Example: delete-itinerary-attraction 1day/2" and the second line: "delete-itinerary-attraction: Deletes the attraction identified by the index ofattraction in the selected itinerary."

User can add an attraction to an itinerary after listing itineraries, when he/she is no longer knows which itinerary was selected. This can be reproduced by selecting an existing itinerary, then listing the itinerary, then executing a valid add-itinerary-attraction command. It would add the attraction to the previously selected itinerary, which the user may not be sure of.

Above image is when an itinerary is not selected.

Above image is after executing the add-itinerary-attraction command