This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
| var path = require('path'); | |
| var Nightmare = require('nightmare'); | |
| var should = require('chai').should(); | |
| describe('Nightmare demo', function () { | |
| this.timeout(15000); // Set timeout to 15 seconds, instead of the original 2 seconds | |
| var url = 'http://localhost:3000'; | |
| describe('Start page', function () { |
Just migrated it from Codepen.io to markdown. Credit goes to David Conner.
| Working with DOM | Working with JS | Working With Functions |
|---|---|---|
| Accessing Dom Elements | Add/Remove Array Item | Add Default Arguments to Function |
| Grab Children/Parent Node(s) | Add/Remove Object Properties | Throttle/Debounce Functions |
| Create DOM Elements | Conditionals |
An important part of "routing" is handling redirects. Redirects usually happen when you want to preserve an old link and send all the traffic bound for that destination to some new URL so you don't end up with broken links.
The way we recommend handling redirects has changed in React Router v6. This document explains why.
In React Router v4/5 (they have the same API, you can read about why we had to bump the major version here) we had a <Redirect> component that you could use to tell the router when to automatically redirect to another URL. You might have used it like this:
This gist contains a short assignment I'd like everyone to complete before our formal lesson. The prework involves reading some of the React Router documentation, and will allow us to keep the lesson more hands on.
You will not be turning this in; it's for your own understanding/learning/benefit 😁
⇐ back to the gist-blog at jrw.fi
Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.
I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.
This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso
| 71, Hannibal Buress: Animal Furnace | |
| 80, Hannibal Buress: Comedy Camisado | |
| 17, Meet My Valentine | |
| 55, Experimenter | |
| 75, French Dirty | |
| 11, Love | |
| 7, I Love You Phillip Morris | |
| 9, A Ballerina's Tale | |
| 67, Hellions | |
| 65, The Land Before Time XIV: Journey of the Brave |
If you find a company where you're interested in applying for work, here are some steps you can follow to see if any of your instructors know someone at the company, or know someone who knows someone, etc.
(instructions are accurate as of late August 2020, but subject to change if LinkedIn changes their UI)
Fork this CodePen.
Without editing the HTML, make the site look like this:
