Samuel Silva

Fixed just forcing a display: inline after some event, like so: ``` success: function(response, newValue) { $(this).css('display', 'inline'); } ```

@mbenford Why dont you merge this commit in: https://github.com/wizbii/ngTagsInput/commit/6ef8959abcaaf545d743dfab5c0cbe46903acef8 Even using `keyProperty` still getting issues and really wanna use my custom `track by` expression.

That's what I've been wondering, I'm switching to CRA with native babel7/typescript support.

@shobhitg You still can use tslint, just include it manually like: - yarn add tslint tslint-react tslint-whatever-else-you-use - tslint.json in your root - "lint": "tslint -c tslint.json src/**/*.{ts,tsx}" (package.json)

@shobhitg You can call your custom `tslint` script in the `start` one, however this is more a workaround than a recommendation, might be better just wait tslint get official: https://github.com/facebook/create-react-app/pull/5697

Sure, there are several ways to debounce it, and we might not call queries/mutations from onChange events, I just think that this would be super helpful if implemented directly in...

Hi @EYHN , the best way to test it would be with `expectSaga` like: ``` it('test', () => { const changeLocaleAction = { type: CHANGE_LOCALE, }; return expectSaga(yourSagaFn) .put(changeLocaleAction(navigator.language)) .put(whateverYouWantToTest)...

Any plans to migrate to `@emotion/styled`?

I fixed up this issue here: https://www.npmjs.com/package/@samuelcastro/react-styled-flexboxgrid

In case the owners of this repo wants to incorporate those changes I've created a PR as well: https://github.com/LoicMahieu/react-styled-flexboxgrid/pull/184