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

Scrum Report #3 (June 20, 2020) #7

Open
jrayo00 opened this issue Jun 20, 2020 · 4 comments
Open

Scrum Report #3 (June 20, 2020) #7

jrayo00 opened this issue Jun 20, 2020 · 4 comments

Comments

@jrayo00
Copy link
Collaborator

jrayo00 commented Jun 20, 2020

No description provided.

@jrayo00
Copy link
Collaborator Author

jrayo00 commented Jun 20, 2020

Last iteration i worked on some styling tweaks, worked out the data structure design of the itinerary that is currently being viewed, and got the delete functionality for items. I ran into some issues with deeply nested objects in redux, but in the end i solved it by normalizing the data similar to a relational database. This next iteration I will be focused on wiring up the components we have, creating the UI for an entire itinerary (not just a city and location), possibly also send itinerary data to our DB.

cs-id: e8m2b

@LaZyLinh
Copy link
Contributor

LaZyLinh commented Jun 21, 2020

Last iteration, I worked on media query of Home page for mobile view, as well as the list component page and its functionalities. I had some issues with iterating through arrays for rendering but was able to fix it with mapping function. However, I still have some issues with rendering efficiency. This iteration, I will fix this issue, finish the list page as well as polishing the frontend with a unified theme.

cs-id:c1q0b

@learese
Copy link
Contributor

learese commented Jun 21, 2020

Last iteration, I worked on the Notes, Location, MapInfo, and Info component for functionality, connected reducers and styling. I added the Notes component that allows users to edit notes. The issue I faced was displaying the results from the Google Maps Place API call, which is called in an async function from MapInfo that gets the location info details, would render an undefined value because the value is displayed before the actual value is stored. Next iteration, I will be working on finalizing the connections between the components, allowing users to upload images in the edit functionality and displaying the location info from the itinerary list and also helping with the database setup probably for database querying.

cs-id: f5a2b

@jkz27
Copy link
Contributor

jkz27 commented Jun 21, 2020

Last iteration, I worked on revamped the map component with a new google map package to fix the Legacy API issue, created reducers and actions to output the state accordingly. Ran into some problem of putting things together with location place details display and still need to investigate the issue. Next iteration, I will be working on helping to put the components together and make sure they function correctly with each other and start hooking up the MongoDB database with the app and probably help to set up API calls.

csid: i0k0b

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

No branches or pull requests

4 participants