<html>
<head>
<script src="https://fb.me/react-with-addons-15.1.0.js"></script>
<script src="https://fb.me/react-dom-15.1.0.js"></script>
<script src="https://cdn.rawgit.com/lodash/lodash/4.5.1/dist/lodash.min.js"></script>
<script src="https://cdn.rawgit.com/lodash/lodash/4.5.1/dist/lodash.fp.min.js"></script>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width">
<title>JS Bin</title>
</head>
<body>
</body>
</html>
/*
what is a good example that shows when to method chain vs.
using flowRight (single line) and flow (multiple lines)?
*/
// the only difference between flow and flowRight is order of invocation.
// flow starts by invoking the function on the left, flowRight starts by
// invoking the function on the right.
// You can use either with both single lines and multiple lines.
//
// Calling it "flowRight" loses meaning when splitting onto multiple lines
// since it's really like "flowBottom". Alex uses `flowRight` for HOC
// composition because HoCs wrap themselves above the BaseComponent, so
// it just is easier to read that way. BTW, `_.flowRight` is an alias for
// `_.compose` in lodash/fp (to make the transition from Ramda easier).
const people = [{ name: 'bob' }, { name: 'alice' }];
const flowExample = _.flow(_.map(_.get('name')), _.first);
const flowRightExample = _.flowRight(_.first, _.map(_.get('name')));
console.log("flow example");
console.log(flowExample(people));
console.log("flowRight example");
console.log(flowRightExample(people));
// I rarely use method chaining:
//
// It also forces me to have the data available up front, as opposed to
// something I can put in a lib (although you can get around that too,
// but why bother?)
//
// Not point-free, so if you get used to this style of FP you will be lost
// in some other FP languages
const firstName =
_(people)
.map(_.get('name'))
.first();
console.log("chaining example")
console.log(firstName);
Output
You can jump to the latest bin by adding /latest
to your URL
Keyboard Shortcuts
Shortcut | Action |
---|---|
ctrl + [num] | Toggle nth panel |
ctrl + 0 | Close focused panel |
ctrl + enter | Re-render output. If console visible: run JS in console |
Ctrl + l | Clear the console |
ctrl + / | Toggle comment on selected lines |
ctrl + ] | Indents selected lines |
ctrl + [ | Unindents selected lines |
tab | Code complete & Emmet expand |
ctrl + shift + L | Beautify code in active panel |
ctrl + s | Save & lock current Bin from further changes |
ctrl + shift + s | Open the share options |
ctrl + y | Archive Bin |
Complete list of JS Bin shortcuts |
JS Bin URLs
URL | Action |
---|---|
/ | Show the full rendered output. This content will update in real time as it's updated from the /edit url. |
/edit | Edit the current bin |
/watch | Follow a Code Casting session |
/embed | Create an embeddable version of the bin |
/latest | Load the very latest bin (/latest goes in place of the revision) |
/[username]/last | View the last edited bin for this user |
/[username]/last/edit | Edit the last edited bin for this user |
/[username]/last/watch | Follow the Code Casting session for the latest bin for this user |
/quiet | Remove analytics and edit button from rendered output |
.js | Load only the JavaScript for a bin |
.css | Load only the CSS for a bin |
Except for username prefixed urls, the url may start with http://jsbin.com/abc and the url fragments can be added to the url to view it differently. |