John Rom

A few months ago I adopted a convention I personally think is preferable to having this feature as a part of `nvm` because it could be used on both Windows...

I don't think I agree with "Round the initial value to the next step" by default. I think that it should be placed exactly where it would be given a...

Thanks for creating those demos, it's very useful! In my opinion, I'd be interested to see if one of the "typescript module generator loaders" work, and see if we can...

@jadbox I think it's definitely important to test using typed module loader wrappers for `css-loader` , but I'd argue that one can fall back to `any` by using a plain...

Hi all, I've created a fork merging @thefill 's changes with the latest `create-react-app-typescript/master` and changed the webpack configs to use the new CRA 2.0 method. Unfortunately, either @thefill 's...

ok, then this PR can be closed, I'll make a reference from my PR to here for documentation purposes. I think my team will stick with the `create-react-app` method, maybe...

I wouldn't be against setting isValidating to true on initial render when validateOnMount is true. It's technically a lie, so we'd have to make sure that if validation never runs...

isInitialValid is now !empty(initialErrors) (though you can continue using isInitialValid for now), so you should be able to do `initialErrors={{ manuallyIndicatingAn: "Error" }}`, or just run your `validate()` function on...

That's reasonable. The only issue I see with it is that some people may regenerate the validationSchema on every render, causing validation on every render, which might cause a state...

This is an upstream issue and a duplicate. There is an issue on React's repository regarding autofill not updating controlled inputs. I'm on mobile, but if you search these issues...