| const Chosed = (props) => { | |
| const elmt = React.useRef() | |
| React.useLayoutEffect(()=>{ | |
| const $elmt = $(elmt.current) | |
| const handleChange = (e) => { | |
| props.onChange(e.target.value); | |
| } | |
| $elmt.chosen() |
| { | |
| "parser": "@typescript-eslint/parser", | |
| "parserOptions": { | |
| "project": "./tsconfig.json", | |
| "tsconfigRootDir": "." | |
| }, | |
| "env": { | |
| "browser": true, | |
| "jest/globals": true | |
| }, |
Feel free to contact me at [email protected] or tweet at me @statisticsftw
This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!
It assumes some knowledge of AWS.
A collection of links to the "Master the JavaScript Interview" series of medium stories by Eric Elliott.
| import React, { PropTypes } from 'react'; | |
| import styled from 'styled-components' | |
| const Wrapper = styled.div` | |
| // styles here that used to be for .test | |
| ` | |
| const Label = styled.label` | |
| // label styles here | |
| ` |
| // Place this with the other middleware inclusion in routes/index.js | |
| keystone.pre('admin', middleware.enforcePermissions); |
| <?php | |
| namespace Bolt\Extension\DesignSpike\ExampleSearch; | |
| use Bolt\Extension\SimpleExtension; | |
| use Bolt\Routing\ControllerCollection; | |
| use Doctrine\DBAL\Query\QueryBuilder; | |
| use Silex\Application; | |
| use Symfony\Component\HttpFoundation\Request; | |
| use Symfony\Component\HttpFoundation\Response; |