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

Mariana-Pipes-Trek #20

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

Conversation

lmarianarp19
Copy link

TREK

Congratulations! You're submitting your assignment!

Comprehension Questions

Question Answer
What does it mean for code to be asynchronous? Asynchronous means that you can do many things at once. For example you can send multiple AJAX request at the same time .
Describe a piece of your code that executes asynchronously. How did this affect the way you structured it? I show all the trip options. At the same time I can make a reservation. I decided to show both things at the same time, so half of the screen will have the trips result at the other half will have the trip details and the option to make a reservation.
What kind of errors might the API give you? How did you choose to handle them? I will have some errors if the url is wrong. I will report this errors to the user.
Do you have any recommendations on how we could improve this project for the next cohort? It will be useful to learn before what is the best way to make validations in a form.

@droberts-sea
Copy link

TREK

What We're Looking For

Feature Feedback
Core Requirements
Git hygiene yes
Comprehension questions yes - Regarding asynchronous code, anything that runs at some unspecified time in the future is asynchronous, including everything from AJAX success / failure callbacks to button click handlers.
Functionality
Click a button to list trips yes
Click a trip to see trip details yes
Fill out a form to reserve a spot yes
Errors are reported to the user yes
Styling, Foundation grid layout yes
Under the Hood
Trip data is retrieved using jQuery AJAX yes
JavaScript is well-organized and easy to read yes - I like that you define most of your event handlers as named functions at the top of the file, and then attach them to events by name.
HTML is semantic mostly - I see several places you use <div> where a more semantic tag would be appropriate.
Overall

Good work overall! In my estimation there are two difficult things in JavaScript we've never had to do in Ruby/Rails:

  • Working with callback functions, especially in an asynchronous context
  • Manipulating the DOM (and structuring the DOM to make it easy to manipulate)

Based on this submission I'd say you have a good handle on them. Both of these topics will get substantially more complex as we continue to build bigger apps with more moving parts, so keep up the focus and hard work!

let details = `
<div class="large-8 columns">
<h2> ${response.name}</h2>
<table>

Choose a reason for hiding this comment

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

Good job wrapping this dynamic content in a sectioning element. Much cleaner than having a bunch of free-floating <p> tags.

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.

2 participants