John de Stigter
John de Stigter
What about this setup: ```typescript import * as React from 'react' import { connect } from 'react-redux' const mapStateToProps = (storeSate: any) => { return { foo: 144 } }...
I took a stab at the _utils_ package: https://github.com/emotion-js/emotion/pull/2359
I've currently solved the problem by pointing `linter-flow` to a bash script that redirects the request: ``` #!/bin/bash DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" $DIR/../node_modules/.bin/flow $1 $DIR/../dom/...
I tried with ```ts [ '@babel/plugin-transform-typescript', { isTSX: true }], '@babel/plugin-transform-react-jsx', ] ``` First without `isTSX: true` but that didn't make a difference. Setting `isTSX` to true seems to resolve...
> The current workaround would probably to put your files with machines in files which don't export JSX files or CSS files. How painful is that for you? Not at...
I think I might be having the same issue. When my test fails the node server isn't shut down and I have to manually kill it before running the tests...
Ready for initial review, especially design review. A [follow-up PR](https://github.com/GetJobber/atlantis/pull/1600) implements this for _InputDate_ and I'll have another one for _DatePicker_ (_CalendarDatePicker_ + an activator) I want to add some...
I avoided making it dependant on `date-fns` as well. Not sure if we have thoughts on that. My opinion is that it's okay to have the few util functions defined...
Todo: Implement style for todays date
Running into this as well in 3.11.8