- access a deployed version of the website so I can browse and purchase products.
- view all available products so I can pick from a variety.
- view a single product so I can see more details.
- add a product to my cart so I can collect my desired products in one place.
- edit my cart if I change my mind:
Introduce what the project is, the story behind it and what interested in you the project.
If you have something to present, walk everyone through a user story of your app. Or if you don't have a user story, you can walk through the working parts of your app. Or if you really don't have much to show, a slide deck of a few slides of what you were trying to would suffice.
Your presentation will be given to your instructor and assigned fellow, plus any other available staff. It will include a general overview / demo of your application followed by various code-focused sections. The whole presentation should last no more than 11 minutes. Practice beforehand to calibrate how much time that is!
Show a single basic & fast run-through of your application from first-time visitor to ordering a product(s). Highlight what is unique about your application and thoughts behind the decisions made regarding features and user experience (includes visual structure and design). We recommend having demo screens / tabs already set up so you do not waste time, e.g. typing in long forms.
High level overview: pull latest master, make a branch, commit changes, push to GitHub, make a PR, get it approved, merge it to master. Rinse and repeat.
- Make issue corresponding to feature
git checkout mastergit pullto get master up to dategit checkout -b YOUR-NEW-BRANCH-NAMEto switch to a new branch
| for (var x = 0; x < 3; x++) { | |
| setTimeout(() => console.log(x), 100); | |
| } |
| console.log('Hellow') | |
| setTimeout(() => { console.log('a new') }, 5000) | |
| console.log('World') |
A test-spec-based assessment (similar to previous checkpoints, e.g. pillars) covering: Express, Sequelize, React, Redux, and JS algorithms.
Determining whether you are ready for what's coming in senior phase: whether you will be able to contribute meaningfully to group projects and whether you are in a place to benefit (instead of flounder) from the senior phase curriculum.
A reasonably large solo project you will work on during week 5 of junior phase.
Determining whether you are ready for what's coming in senior phase: whether you will be able to contribute meaningfully to group projects and whether you are in a place to benefit (instead of flounder) from the senior phase curriculum.
Below is the plan for the "senior gateway": how we determine whether you are ready to continue to senior phase. This will be based heavily on your performance on the "Senior Checkpoint" and as a back-up the "Junior Phase Final Project". Let's talk about the logistics…
The Junior Phase Final Project (JPFP) is, well, a project you will complete SOLO. You will be expected to construct a working full-stack application. We will provide the constraints for what you should build (e.g. "users should be able view all of their uploaded photos"). In order to allow your implementation to be more open-ended and organic, we will not provide automated test specs. 📖 JPFP Study Guide
The Senior Checkpoint is test-spec based and you will also be working solo. To reiterate, instead of providing written-in-English constraints for how it should operate, we will provide automated test spe
Implicit returns: example of how you’d use () => ({ }) syntax with a multi-line function? How does it know which expression to return?
Answer: https://medium.com/@bunlong/arrow-functions-return-rules-in-javascript-b63ed5f25994 Check this out Barish! It looks like “multiline” just represents one statement spread out on multiple lines for implicit return. I believe you only can still have one item/variable/param/arg returned via the multiline implicit.
Is there a way to define properties with JSX expressions that include evaluated expressions inside strings like we usually do using template literals? (e.g. className=${value} otherClass). The only method I found searching around was to define the string elsewhere and then plug it in as a single evaluated expression.
Answer: You should be able to still use template literal expressions like this: