Boris Cherny

This is an interesting idea. I went ahead and implemented it as an experiment in [this PR](https://github.com/bcherny/undux/pull/52/files). Three downsides of this sort of setter syntax: 1. We can't use curried...

@hackerxian I did, and thanks for bringing it up! Both syntaxes are great (in fact we could easily support all 3), but there are a few small downsides, I think:...

@zhy0216 There's no way to do that safely, unless we introduce a codegen script.

@hurrymaplelad With this proposed architecture, a lot of things that normally live in effects would live in action creators (aka. utility functions) instead. This makes Undux look a lot like...

Would come in handy here too http://stackoverflow.com/questions/36900619/how-do-i-express-this-in-typescript

In case it's helpful for anyone else, I dropped down to ssh as a quick hack to unblock myself (in addition to double-checking the authorized_keys on my DigitalOcean droplet): ```...

Circling back after reading through the discussion, here's what I'd suggest: 1/ Currently, when your input `-i` is a glob and you specify and output `-o` directory, we flatten the...

@matt1097 PRs for https://github.com/bcherny/json-schema-ref-parser are welcome. I also see a reasonable suggestion on your PR -- could using Node's `path` library simplify some of the cross-platform logic?

We don't take `format` into account when inferring a schema's type. Without a full example, I'm not sure why you're getting `string` at all. To get `string`, add `"type": "string"`...

We have a [test case](https://github.com/bcherny/json-schema-to-typescript/blob/master/test/e2e/emptyProperties.ts) covering this. But for the life of me I don't remember where in the spec I saw that this is the correct behavior. Reading it...