git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git
cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream
'use strict'; | |
var React = require('react-native'); | |
var Firebase = require('firebase'); | |
var { | |
AppRegistry, | |
StyleSheet, | |
Text, | |
View, | |
TextInput, |
var CryptoJS = require('crypto-js'); | |
function uploadImage(uri) { | |
let timestamp = (Date.now() / 1000 | 0).toString(); | |
let api_key = 'your api key' | |
let api_secret = 'your api secret' | |
let cloud = 'your cloud name' | |
let hash_string = 'timestamp=' + timestamp + api_secret | |
let signature = CryptoJS.SHA1(hash_string).toString(); | |
let upload_url = 'https://api.cloudinary.com/v1_1/' + cloud + '/image/upload' |
Lightning talk proposal for the Reactive 2016 Conference. Here's a handy retweet link
When I started writing React apps, I approached components as if they were “just the V in MVC!” Seriously, we’ve all heard it.
I have found this to be an inferior way of thinking about and building React applications. It makes people treat React as a drop-in replacement for something like a Backbone or Angular 1.x View. In other words, people treat it like a glorified template system with partials and don’t harness the power of its functional paradigms.
{ | |
"emojis": [ | |
{"emoji": "👩👩👧👧", "name": "family: woman, woman, girl, girl", "shortname": ":woman_woman_girl_girl:", "unicode": "1F469 200D 1F469 200D 1F467 200D 1F467", "html": "👩‍👩‍👧‍👧", "category": "People & Body (family)", "order": ""}, | |
{"emoji": "👩👩👧👦", "name": "family: woman, woman, girl, boy", "shortname": ":woman_woman_girl_boy:", "unicode": "1F469 200D 1F469 200D 1F467 200D 1F466", "html": "👩‍👩‍👧‍👦", "category": "People & Body (family)", "order": ""}, | |
{"emoji": "👩👩👦👦", "name": "family: woman, woman, boy, boy", "shortname": ":woman_woman_boy_boy:", "unicode": "1F469 200D 1F469 200D 1F466 200D 1F466", "html": "👩‍👩‍👦‍👦", "category": "People & Body (family)", "order": ""}, | |
{"emoji": "👨👩👧👧", "name": "family: man, woman, girl, girl", "shortname": ":man_woman_girl_girl:", "unicode": "1F468 200D 1F469 200D 1F467 200D 1F467", "html": "👨‍👩&z |
import React from 'react'; | |
import { connect } from 'formik'; | |
class ErrorFocus extends React.Component { | |
componentDidUpdate(prevProps) { | |
const { isSubmitting, isValidating, errors } = prevProps.formik; | |
const keys = Object.keys(errors); | |
if (keys.length > 0 && isSubmitting && !isValidating) { | |
const selector = `[id="${keys[0]}"]`; | |
const errorElement = document.querySelector(selector); |
EDIT: DO NOT USE THIS. THIS WAS FROM WHEN ALL OF THIS WAS NEW/EXPERIMENTAL AND NOT OFFICIALLY SUPPORTED. PLEASE SEE THE LINK BELOW FOR THE PROPER, EASIER INTEGRATION NOWADAYS =)
Use create-nuxt-app
and enable the Typescript related options to scaffold a new boilerplate TS Nuxt repo:
yarn create nuxt-app
// when T is any|unknown, Y is returned, otherwise N | |
type IsAnyUnknown<T, Y, N> = unknown extends T ? Y : N; | |
// when T is never, Y is returned, otherwise N | |
type IsNever<T, Y = true, N = false> = [T] extends [never] ? Y : N; | |
// when T is a tuple, Y is returned, otherwise N | |
// valid tuples = [string], [string, boolean], | |
// invalid tuples = [], string[], (string | number)[] |
/** | |
* Requires jsdoc and jsdoc-to-markdown | |
*/ | |
/* eslint-disable no-console */ | |
const fs = require('fs') | |
const path = require('path') | |
const glob = require('glob') | |
const { execSync } = require('child_process') | |
const jsdoc2md = require('jsdoc-to-markdown') |