Yao Zhao

Hello, Facebook guys, in fact this issue causes a **SERIOUS** problem: we can't update input asynchronously with Chinese input. For example, we can't use meteor reactive datasources or stores like...

@eyesofkids nice work, this could be made as the default implementation of `onChange` for input, textarea ...

> This behavior does not work for plugins, Should it work? That way plugins can have more control over the behavior.

+1 for regex(or someway to check string pattern) and spec. This is already an old issue, is there any thought for this?

> 同名 reducer 和 effect 不会 fallthrough（即两者都执行），而是仅执行 effect 这个改动感觉是设计被实现牵着鼻子走了。这个breaking change的解释竟然是因为[另一处升级而导致的副作用](https://github.com/sorrycc/blog/issues/48#issuecomment-326883877)？实在是匪夷所思。且不论原因，这个设计上的变化也是不合理的。 所谓effects，可以理解为side effects，其为action的伴随效果，或副作用，表现为对action（reducer）进行纯扩展（不改动原有逻辑，而增加扩展逻辑，支线逻辑，旁路逻辑，或曰，副逻辑），这自然而然。而这个breaking change改变了这个设定，让effects实际上变成了async action，实在不妥，不仅破坏了api的兼容性，而且逻辑和命名也反而变得矛盾了。 其实async action并非不好，但这次升级完全可以通过增加async action的方式来实现，而非改变一个定义准确的概念还破坏了兼容性。我觉得这个breaking change是dva2设计上的灾难。

@yangbin1994 例如做一个log或者发一个数据统计。或者，状态是改成requesting-data，而side effect是实际执行拉取动作，完成后更新状态为data-fetched或failed。 用例是一方面，关键是一个功能的效果应该是和其概念定义保持。如果觉得没有这个用例，那大可不要这个feature，而做一个async action的feature，而不是因为图方便而混淆概念。

@xcodebuild 你好，请问能指点下如何配置 proxifier 吗，我这里尝试了一下没有成功

@steveruizok no, `logged in` is very good for me, :) look forward to it.

Cool~ look forword to The problem of current `extend` workaround is, we have to have knowledge of the original field to make it again, which is duplicated and weak.

is there any solution for this case? in electron, worker should have the same externals with the renderer