不需要给 .setData() 传入整个 state，只传入变化的值就行了 #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OpenGG
commented
Oct 21, 2016
OpenGG
commented
- setData() 内部有深度复制逻辑， shallowEqual() 不管用的
- 由于上述原因，每一次触发 store 改变，都会导致所有页面数据被刷新
- setData() 涉及到跨线程通信/序列化等，开销不小，传入的对象太大，性能上有问题
Weapp use deep cloning in .setData() internally, so mappedState will never be shallow equal to data. In another word, shallowEqual(this.data, mappedState) will always return false. By tracking states in connect(), we can get patches between states, which can be later applied to .setData().
|
不好意思，这两天比较忙，一直没时间看。 |
|
如果是更深的嵌套数据还是会去clone整个key吧 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.