timwangmusic / vacation-planner Goto Github PK

When a new set of travel plans are generated, they can be found only through a parent Redis key, which expires in 24 hours (by current config). After the parent key expires, the plans cannot be referenced easily unless through saved plans list in the user profile. When users delete the references, they are likely to accumulate in the database. This is a flaw of the original design.

When querying with precise location feature, and save the results to user profile leads to the title being the lat/lng of the query.

The way mongodB is being installed in the README file may not work anymore

MacBook-Pro:Vacation-Planner sandeepanand$ brew install mongodb Error: No available formula with the name "mongodb"

The installation works as a tap now,
https://docs.mongodb.com/manual/tutorial/install-mongodb-on-os-x/

Often times we start planning a day trip with one Point of Interest (POI) in mind. For instance, we are in New York City and want to visit the Empire state building. But we don't know what are the nearby POI to go that can fill in the day. Vacation planner should be able to fill the plan for the rest of the day for users.

Back button does not work in the mobile version on some browser.

Description:

For the trip result show page merged to master from 96179ae, there are some trip plan show page with missing place photo.

Link: https://www.unwind.dev/v1/plans/34166aa9-ac7b-4505-b750-d5c93d9b975f?

Things to debug:

• study the cause of this missing picture issue, initial assessment it is due to invalid location info stored in Redis
• work out a fix pending on the determination of the issue

figure out the reason why a few places may have broken photo on the plan detail page.

Add a thumb up and thumb down button besides each plan so that the server should remove the plan from next rendering for that user.

To support this feature, we have to increase the number of plans generated from the initial request. The reason is otherwise we have to keep generating new plans, which will bog down the server.

In PR #213, TravelDate is enabled as a part of the URL parameter.
Currently there is no logic to handle if an invalid plan show page URL with fake travel date.

For the case of free Choice, mostly chosen, a user may see results in the responses where there are rows in a plan, where there the plan has selections which are not free .

Especially it's tough to get free options for eateries or Clubs

Some of our APIs lack sanitization and input validations, these can lead to security vulnerabilities such as cross site scripting attacks.

Description:

For the new PR merged to master in 96179ae and service endpoint /plans/:id, there are some trip plans with incorrect sequences of locations.
For example, the restaurant location can be shown in the last instead of middle.

Things to debug

• check original solutions and trip plans stored in Redis, and see if the location and place ID mapping is correct
• check processing of new endpoint handler getTripDetails(), if any processing may have swapped the order of locations

Starting from 8831b78, the price selection from home page seems to have an offset of 1 compared to the search results from backend.