value | name |
---|---|
100 | extralight/ultralight |
200 | light/thin |
300 | book/demi/light |
400 | regular/normal |
500 | medium |
600 | semibold/demibold |
// === Arrays | |
var [a, b] = [1, 2]; | |
console.log(a, b); | |
//=> 1 2 | |
// Use from functions, only select from pattern | |
var foo = () => [1, 2, 3]; |
{ | |
// http://eslint.org/docs/rules/ | |
"ecmaFeatures": { | |
"binaryLiterals": false, // enable binary literals | |
"blockBindings": false, // enable let and const (aka block bindings) | |
"defaultParams": false, // enable default function parameters | |
"forOf": false, // enable for-of loops | |
"generators": false, // enable generators | |
"objectLiteralComputedProperties": false, // enable computed object literal property names |
Use these rapid keyboard shortcuts to control the GitHub Atom text editor on macOS.
- ⌘ : Command key
- ⌃ : Control key
- ⌫ : Delete key
- ← : Left arrow key
- → : Right arrow key
- ↑ : Up arrow key
// Component.js | |
const Component = props => ( | |
<MyContext.Consumer> | |
{(context) => ( | |
<Foo | |
bar={props.bar} | |
baz={context.baz} | |
/> | |
)} | |
</MyContext.Consumer> |
React recently introduced an experimental profiler API. After discussing this API with several teams at Facebook, one common piece of feedback was that the performance information would be more useful if it could be associated with the events that caused the application to render (e.g. button click, XHR response). Tracing these events (or "interactions") would enable more powerful tooling to be built around the timing information, capable of answering questions like "What caused this really slow commit?" or "How long does it typically take for this interaction to update the DOM?".
With version 16.4.3, React added experimental support for this tracing by way of a new NPM package, scheduler. However the public API for this package is not yet finalized and will likely change with upcoming minor releases, so it should be used with caution.
class Muyian extends Date { | |
to (date, locale) { | |
return this.diff(date, true); | |
} | |
form (date, locale) { | |
return this.diff(date, true); | |
} |
Download BotFramework emulator: https://github.com/microsoft/BotFramework-Emulator/releases | |
SLIDES: https://github.com/Blesfia/nodeconf-template/blob/master/slides.pdf | |
1. (10:00-10:15m) Start: git clone https://github.com/Blesfia/nodeconf-template.git | |
2. (10:15-10:30m) Console bot: git checkout -q 01-console | |
3. (10:30-10:45m) BotFramework Adapter: git checkout -q 02-bframework-emulator | |
4. (10:45-10:50m) Bot Memory: git checkout -q 03-memory | |
Note: You will have to change the google.json in the repository to use Dialogflow, the actual key is not working to avoid security problems. ;) | |
5. (10:50-11:00m) Recognizer: git checkout -q 04-nlu | |
6. (11:00-11:10m) Waterfall: git checkout -q 05-dialogs |
Todo el mes de febrero estaremos tratando sobre grafos, a continuación los recursos de cada una de las sesiones
- Ene 26 - Introducción a Grafos y Representación
- Feb 02 - BFS (Breadth First Search)
- Feb 09 - Flood-fill y DFS (Depth First Search)
- Feb 16 - Ordenamiento Topológico
- Feb 23 - Kosaraju
Las grabaciones quedan https://www.youtube.com/playlist?list=PLRMfC7A6yJWqJ6x-Xw4Fmrpx-4N5wPjQH