Open
Conversation
…ally-created elements with .on
TREKWhat We're Looking For
|
dHelmgren
reviewed
Jun 14, 2019
| detailsList.append(`<li><strong>Continent</strong>: ${details.continent}</li>`); | ||
| detailsList.append(`<li><strong>Category</strong>: ${details.category}</li>`); | ||
| detailsList.append(`<li><strong>Weeks</strong>: ${details.weeks}</li>`); | ||
| detailsList.append(`<li><strong>Cost</strong>: ${details.cost}</li>`); |
There was a problem hiding this comment.
I'd put all this dom manipulation in a helper!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TREK
Congratulations! You're submitting your assignment!
Comprehension Questions
axiosrequests are asynchronous. In past units, we could handle success and error cases in a separateif-elsestatement. When usingaxios, though, we need to chain these success and error cases using.thenand.catch.Tripin the list by it's ID field. Would it be advantageous to keep the list in order by the id field? Explain why or why not.event.target. This selector gives us access to information associated with that element. So, the order in which the trips are list in doesn't matter.