Dan Schuman

Seems like the issue happened between 6.0.1 and 6.1.0

I believe I was able to write a test that replicates it maybe... but I hit a wall at what was going wrong.

A workaround is to put some kind of `await sleep(1)` statement in `onSubmit` =\

I would LOVE that, however, we are currently limited by the Bucklescript's internal memory representation of records/variants as arrays; we don't have record keys available for serialization. Related: https://github.com/BuckleScript/bucklescript/pull/2690 and...

The reasoning behind records as arrays is that Bucklescript is _very_ performance optimized, and working with arrays has a lot of performance benefits. From what I'm aware, debug output (which...

Re: interop, there are mechanisms available for userland Records=>JS.Object: https://bucklescript.github.io/docs/en/generate-converters-accessors.html#convert-between-jst-object-and-record These require opt-in by the user, however, and aren't good for the general case such as this.

This is a great discussion to be had! I'm a _huge_ fan of Redux. In my work, it has offered me these advantages: ### Preventing prop-passing and unnecessary coupling via...

Looks like this line here filters out `undefined`: https://github.com/facebook/jest/blob/master/packages/jest-config/src/setFromArgv.ts#L18 One option would be to allow `undefined` for whitelisted keys?

Would a PR along the lines of this be acceptable? ```tsx const undefinedWhitelist = ['coverage']; // ...snip const argvToOptions = Object.keys(argv) .filter( key => (argv[key] !== undefined || undefinedWhitelist.includes(key)) &&...

bah, I suppose that would break it for anyone who doesn't explicitly provide `--coverageFrom` option, then..