blocks|key|500453|text|UPD：它现在是ES2018的一部分|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|500454|它可能会通过一个然而属性扩展了语法略有改进。|500455|return+{
++++...state,
++++notificationBar:+{
++++++++...state.notificationBar,
++++++++open:+true,
++++},
};|code-block|syntax|javascript|500456|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/sebmarkbage/ecmascript-rest-spread/blob/master/Spread.md#object-spread-initializer^0|0|3|0|8|9|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|I|5|J|7|11|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

<p><strong>UPD</strong>: it's now a part of the ES2018</p>

<p>It might be slightly improved via a <a href="https://github.com/sebmarkbage/ecmascript-rest-spread/blob/master/Spread.md#object-spread-initializer" rel="noreferrer"><strong>non-standardised</strong> yet properties spread syntax</a>:</p>

<pre><code>return {
    ...state,
    notificationBar: {
        ...state.notificationBar,
        open: true,
    },
};
</code></pre>


blocks|key|276715|text|虽然可以使用spread操作符，但是还有很多其他方法可以实现相同的结果，甚至不需要将来的JS编译器来实现非标准化的特性。以下是一些没有特定顺序的其他选项。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|276716|返回文字|276717|如果您确信您的状态不会增长，那么只需将整个新状态作为文字返回即可。|276718|return+{
++notificationBar:+{
++++open:+true
++}
}|code-block|syntax|javascript|276719|然而，这并不经常是合适的，因为你的状态不太可能如此简单。|276720|联合收割机|276721|Redux为您提供了一个实用方法，用于组合几个在状态对象的不同部分上工作的还原器。在本例中，您将创建一个单独处理此对象的notificationBar还原器。|offset|length|style|CODE|276722|+createStore(combineReducers({
+++notificationBar:+function(state=initialNBarState,+action)+{
+++++switch+(action.type)+{
+++++++case+actions.LAYOUT_NOTIFICATIONBAR_OPEN:
+++++++++return+Object.assign({},+state,+{+open:+true+});
+++}
+});|276723|这使您不必担心顶级属性，这样您就可以避免嵌套对Object.assign的调用。|276724|如果您的状态在逻辑上可以分解为明确定义的部分，那么这可能是解决这个问题的最惯用的方法。|276725|使用不可变数据|276726|可以使用持久数据结构库创建数据结构，而不是修改以返回副本。|276727|莫里|276728|Mori是将Clojure的数据结构和functional编译成JS的结果。|276729|import+{+hashMap,+updateIn+}+from+'mori';

const+initialState+=+hashMap(
++"notificationBar",+hashMap(
++++"open",+false
++)
);

//+...

return+updateIn(state,+['notificationBar',+'open'],+true);|276730|ImmutableJS|276731|ImmutableJS是一种更必要的方法，可以将哈希数组映射的尝试的语义从Clojure的持久数据结构转移到Javascript。|276732|import+{+Map+}+from+'immutable';

const+initialState+=+Map({
++notificationBar:+Map({
++++open:+true
++});
});

//+...

return+state.setIn(['notificationBar',+'open'],+true);|276733|别名Object.assign|276734|您可以创建一个更友好的Object.assign版本来编写上面代码的简洁版本。实际上，它几乎可以和...运算符一样简洁。|276735|function+$set(...objects)+{
++return+Object.assign({},+...objects);
}

return+$set(state,+{
++notificationBar:+$set(state.notificationBar,+{
++++open:+true,
++})
});|276736|使用不变的帮手|276737|还有许多库也提供了对常规可变对象进行修改的不可变帮助程序。|276738|更新|276739|React在很长一段时间内都有一套不变的帮手。它们使用与MongoDB查询类似的语法。|276740|import+update+from+'react-addons-update';

return+update(state,+{
++notificationBar:+{
++++open:+{+$set:+true+}
++}
});|276741|道具不可变|276742|此库允许您使用熟悉的点路径来指定(嵌套)属性的更新。|276743|import+dotProp+from+'dot-prop-immutable';

return+dotProp.set(state,+'notificationBar.open',+true);|276744|最新情况|276745|这个库是react-addons-update的包装器，它为更新(嵌套)属性提供了更多的功能语法。|276746|不是传递一个新值，而是传递一个接受旧值并返回新值的函数。|276747|import+updateIn+from+'update-in';

return+updateIn(state,+['notificationBar',+'open'],+()+=>+true);|276748|不可变路径|276749|对于更新属性，此库类似于dot-prop-immutable和update-in之间的交叉。|276750|import+path+from+'immutable-path';

return+path.map(state,+'notificationBar.open',+()+=>+true);|276751|entityMap^0|0|0|0|0|0|0|1O|F|0|0|N|D|0|0|0|0|0|0|0|0|0|0|2|D|0|B|D|1D|3|0|0|0|0|0|0|0|0|0|0|0|4|J|0|0|0|0|C|I|V|9|0|0^^$0|@$1|2|3|4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2K|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|2L|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|2M|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|2N|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|2O|8|@$Q|2P|R|2Q|S|T]]|9|@]|A|$]]|$1|U|3|V|5|H|7|2R|8|@]|9|@]|A|$I|J]]|$1|W|3|X|5|6|7|2S|8|@$Q|2T|R|2U|S|T]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2V|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2W|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|2X|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2Y|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|18|3|19|5|H|7|30|8|@]|9|@]|A|$I|J]]|$1|1A|3|1B|5|6|7|31|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|32|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|H|7|33|8|@]|9|@]|A|$I|J]]|$1|1G|3|1H|5|6|7|34|8|@$Q|35|R|36|S|T]]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|37|8|@$Q|38|R|39|S|T]|$Q|3A|R|3B|S|T]]|9|@]|A|$]]|$1|1K|3|1L|5|H|7|3C|8|@]|9|@]|A|$I|J]]|$1|1M|3|1N|5|6|7|3D|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|3E|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|6|7|3F|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|3G|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|H|7|3H|8|@]|9|@]|A|$I|J]]|$1|1W|3|1X|5|6|7|3I|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|6|7|3J|8|@]|9|@]|A|$]]|$1|20|3|21|5|H|7|3K|8|@]|9|@]|A|$I|J]]|$1|22|3|23|5|6|7|3L|8|@]|9|@]|A|$]]|$1|24|3|25|5|6|7|3M|8|@$Q|3N|R|3O|S|T]]|9|@]|A|$]]|$1|26|3|27|5|6|7|3P|8|@]|9|@]|A|$]]|$1|28|3|29|5|H|7|3Q|8|@]|9|@]|A|$I|J]]|$1|2A|3|2B|5|6|7|3R|8|@]|9|@]|A|$]]|$1|2C|3|2D|5|6|7|3S|8|@$Q|3T|R|3U|S|T]|$Q|3V|R|3W|S|T]]|9|@]|A|$]]|$1|2E|3|2F|5|H|7|3X|8|@]|9|@]|A|$I|J]]|$1|2G|3|-4|5|6|7|3Y|8|@]|9|@]|A|$]]]|2H|$]]

<p>Although it's possible to use the spread operator, there are lots of other ways to achieve the same result without even needing a future JS compiler for a non standardised feature. Here are some other options in no particular order.</p>

<h1>Return a Literal</h1>

<p>If you are sure that your state won't grow, then you can simply return the entire new state as a literal.</p>

<pre><code>return {
  notificationBar: {
    open: true
  }
}
</code></pre>

<p>However, that's not often going to be appropriate because it's unlikely that your state will be this simple.</p>

<hr>

<h1>Combine Reducers</h1>

<p>Redux gives you a utility method for combining several reducers that work on different parts of the state object. In this case, you'd create a <code>notificationBar</code> reducer that handled this object alone.</p>

<pre><code> createStore(combineReducers({
   notificationBar: function(state=initialNBarState, action) {
     switch (action.type) {
       case actions.LAYOUT_NOTIFICATIONBAR_OPEN:
         return Object.assign({}, state, { open: true });
   }
 });
</code></pre>

<p>This prevents you from having to worry about the top level of properties, so that you can avoid nesting calls to <code>Object.assign</code>.</p>

<p>If your state can logically broken down into clearly defined sections then this is probably the most idiomatic way to solve this problem.</p>

<hr>

<h1>Use Immutable Data</h1>

<p>You can use an persistent data structures library to create data structures than can be modified to return a copy.</p>

<h2>Mori</h2>

<p>Mori is the result of compiling Clojure's data structures and functional API into JS.</p>

<pre><code>import { hashMap, updateIn } from 'mori';

const initialState = hashMap(
  "notificationBar", hashMap(
    "open", false
  )
);

// ...

return updateIn(state, ['notificationBar', 'open'], true);
</code></pre>

<h2>ImmutableJS</h2>

<p>ImmutableJS is a more imperative approach to bringing the semantics of Hash Array Mapped Tries from Clojure's persistent data structures to Javascript.</p>

<pre><code>import { Map } from 'immutable';

const initialState = Map({
  notificationBar: Map({
    open: true
  });
});

// ...

return state.setIn(['notificationBar', 'open'], true);
</code></pre>

<hr>

<h1>Alias <code>Object.assign</code></h1>

<p>You can create a friendlier version of <code>Object.assign</code> to write terser versions of the code above. In fact, it can be nearly as terse as the <code>...</code> operator.</p>

<pre><code>function $set(...objects) {
  return Object.assign({}, ...objects);
}

return $set(state, {
  notificationBar: $set(state.notificationBar, {
    open: true,
  })
});
</code></pre>

<hr>

<h1>Use Immutable Helpers</h1>

<p>There are a number of libraries that also offer immutability helpers for making modifications to regular mutable objects.</p>

<h2>react-addons-update</h2>

<p>React has had a built in set of immutability helpers for a long time. They use a similar syntax to MongoDB queries.</p>

<pre><code>import update from 'react-addons-update';

return update(state, {
  notificationBar: {
    open: { $set: true }
  }
});
</code></pre>

<h2>dot-prop-immutable</h2>

<p>This library allows you to use familiar dot paths to specify updates to (nested) properties.</p>

<pre><code>import dotProp from 'dot-prop-immutable';

return dotProp.set(state, 'notificationBar.open', true);
</code></pre>

<h2>update-in</h2>

<p>This library is a wrapper around <code>react-addons-update</code> and provides a more functional syntax for updating (nested) properties.</p>

<p>Rather than passing a new value, you pass a function which takes the old value and returns a new one.</p>

<pre><code>import updateIn from 'update-in';

return updateIn(state, ['notificationBar', 'open'], () =&gt; true);
</code></pre>

<h2>immutable-path</h2>

<p>For updating properties, this library is like a cross between <code>dot-prop-immutable</code> and <code>update-in</code>.</p>

<pre><code>import path from 'immutable-path';

return path.map(state, 'notificationBar.open', () =&gt; true);
</code></pre>


blocks|key|278028|text|除了前面所说的，下面是一种使用兰达的功能方法|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|278029|import+{+assocPath+}+from+'ramda';

const+o1+=+{+a:+{+b:+{+c:+1+},+bb:+{+cc:+22+}+}+};
const+o2+=+assocPath(['a',+'b',+'c'])(42)(o1);
console.log(o1+!==+o2,+o1.a+!==+o2.a);+//+new+copies+of+"changed"+objects
console.log(o1.a.bb+===+o2.a.bb);+//+deep+unchanged+properties+are+copied+by+reference|code-block|syntax|javascript|278030|entityMap|0|LINK|mutability|MUTABLE|url|http://ramdajs.com/^0|F|2|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|C|$G|H]]|$1|I|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

<p>In addition to what've been said earlier, here is a functional way with <a href="http://ramdajs.com" rel="nofollow">Ramda</a>:</p>

<pre><code>import { assocPath } from 'ramda';

const o1 = { a: { b: { c: 1 }, bb: { cc: 22 } } };
const o2 = assocPath(['a', 'b', 'c'])(42)(o1);
console.log(o1 !== o2, o1.a !== o2.a); // new copies of "changed" objects
console.log(o1.a.bb === o2.a.bb); // deep unchanged properties are copied by reference
</code></pre>


blocks|key|500613|text|你可以用镜片。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|500614|import+{+set,+makeLenses+}+from+'@DrBoolean/lenses'

const+L+=+makeLenses(['notificationBar',+'open']);
const+notificationBarOpen+=+compose(L.notificationBar,+L.open)
const+setNotificationBarOpenTrue+=+set(notificationBarOpen,+true)

const+a+=+{+notificationBar:+{+open:+false+}+}
const+b+=+setNotificationBarOpenTrue(a)+
//+`a`+is+left+unchanged+and+`b`+is+`{+notificationBar:+{+open:+true+}+}`|code-block|syntax|javascript|500615|您可以将镜头视为组合属性访问/更新。|500616|关于镜片的一些好资源：|500617|视频+镜头快速污垢|unordered-list-item|offset|length|style|BOLD|500618|实用文章+镜头和虚拟DOM支持开放封闭|500619|视频+非数学家的函数式编程模式|500620|关于合并带imutable.js的透镜的文章|500621|如果您可以阅读lisps，我也会建议您看看这个优秀的介绍的镜头从球拍文档。最后，如果您想深入阅读haskell，您可以查看：镜片.组合数据存取和操作。|500622|entityMap|0|LINK|mutability|MUTABLE|url|https://vimeo.com/104807358|1|http://joneshf.github.io/programming/2015/12/19/Lenses-and-Virtual-DOM-Support-Open-Closed.html|2|https://www.youtube.com/watch?v=AvgwKjTPMmM|3|https://medium.com/@drboolean/lenses-with-immutable-js-9bda85674780|4|http://docs.racket-lang.org/lens/lens-guide.html|5|https://skillsmatter.com/skillscasts/4251-lenses-compositional-data-access-and-manipulation^0|0|0|0|0|0|2|3|6|0|0|0|4|5|E|1|0|0|2|3|C|2|0|0|M|4|F|3|0|7|5|Q|5|1C|7|W|4|4|1Q|C|5|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1I|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1J|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1K|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1L|8|@$N|1M|O|1N|P|Q]]|9|@$N|1O|O|1P|1|1Q]]|A|$]]|$1|R|3|S|5|M|7|1R|8|@$N|1S|O|1T|P|Q]]|9|@$N|1U|O|1V|1|1W]]|A|$]]|$1|T|3|U|5|M|7|1X|8|@$N|1Y|O|1Z|P|Q]]|9|@$N|20|O|21|1|22]]|A|$]]|$1|V|3|W|5|M|7|23|8|@$N|24|O|25|P|Q]]|9|@$N|26|O|27|1|28]]|A|$]]|$1|X|3|Y|5|6|7|29|8|@$N|2A|O|2B|P|Q]|$N|2C|O|2D|P|Q]|$N|2E|O|2F|P|Q]]|9|@$N|2G|O|2H|1|2I]|$N|2J|O|2K|1|2L]]|A|$]]|$1|Z|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]]|10|$11|$5|12|13|14|A|$15|16]]|17|$5|12|13|14|A|$15|18]]|19|$5|12|13|14|A|$15|1A]]|1B|$5|12|13|14|A|$15|1C]]|1D|$5|12|13|14|A|$15|1E]]|1F|$5|12|13|14|A|$15|1G]]]]

<p>You can use Lenses.</p>

<pre><code>import { set, makeLenses } from '@DrBoolean/lenses'

const L = makeLenses(['notificationBar', 'open']);
const notificationBarOpen = compose(L.notificationBar, L.open)
const setNotificationBarOpenTrue = set(notificationBarOpen, true)

const a = { notificationBar: { open: false } }
const b = setNotificationBarOpenTrue(a) 
// `a` is left unchanged and `b` is `{ notificationBar: { open: true } }`
</code></pre>

<p>You can think about Lenses as compositional property access/update.</p>

<p>Some good resources about Lenses:</p>

<ul>
<li><strong>video</strong> <a href="https://vimeo.com/104807358" rel="nofollow noreferrer">Lenses Quick n' Dirty</a></li>
<li><strong>practical article</strong> <a href="http://joneshf.github.io/programming/2015/12/19/Lenses-and-Virtual-DOM-Support-Open-Closed.html" rel="nofollow noreferrer">Lenses and Virtual DOM Support Open Closed</a></li>
<li><strong>video</strong> <a href="https://www.youtube.com/watch?v=AvgwKjTPMmM" rel="nofollow noreferrer">Functional programming patterns for the non-mathematician</a></li>
<li><strong>article</strong> about combining <a href="https://medium.com/@drboolean/lenses-with-immutable-js-9bda85674780" rel="nofollow noreferrer">Lenses with imutable.js</a></li>
</ul>

<p>If you are ok with reading <strong>lisps</strong>, I would also recommend taking look at this excellent <strong>introduction to lenses</strong> from <a href="http://docs.racket-lang.org/lens/lens-guide.html" rel="nofollow noreferrer">racket docs</a>. Finally, if you want to go deeper and are ok with reading <strong>haskell</strong> you can watch: <a href="https://skillsmatter.com/skillscasts/4251-lenses-compositional-data-access-and-manipulation" rel="nofollow noreferrer">Lenses - compositional data access and manipulation</a>.</p>


blocks|key|278157|text|这里的所有建议都是有效的，但我想提出另一种解决方案。这里出现的问题肯定是一个常见的模式，所以我认为最好是为这类更新编写自己的接口，并在减速器内部坚持使用它，并使用一个函数在所有减速器内部进行深入更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|278158|例如，我创建了一个图书馆，我下一次尝试解决这个问题:我得到模块的类型(所谓的“瓷砖”)，函数来执行操作(包括异步和同步)，以及基于传递的参数进行所需的嵌套。所以，就你的情况而言，会是这样的：|offset|length|278159|import+{+createSyncTile+}+from+'redux-tiles';
const+uiTile+=+createSyncTile({
++type:+['ui',+'elements'],
++fn:+({+params+})+=>+params,
++//+type+will+be+`notificationBar`
++nesting:+({+type+})+=>+[type],
});|code-block|syntax|javascript|278160|仅此而已--它将被正确地更新为任意嵌套。此外，瓷砖还提供了选择器，所以您不必亲自担心数据的确切位置，只需使用它们即可。所以，我不想说它是最好的解决方案，但是这个想法很简单--不要害怕编写自己的实现，然后使用工厂来解决这个问题。|278161|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/Bloomca/redux-tiles^0|0|3|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

<p>All advice here are great and valid, but I would like to offer another solution. The problem which appears here is definitely a common pattern, so I think it is much better just to write your own interface for such updates and stick with it inside reducers, and use one function to update deeply inside all your reducers.</p>

<p>For example, <a href="https://github.com/Bloomca/redux-tiles" rel="nofollow noreferrer">I have created a library</a>, where I tried to address this issue the next way: I get the type of the module (so-called "tile"), function to perform operations (both async and sync) and desired nesting based on passed params. So, for your case it will be something like:</p>

<pre><code>import { createSyncTile } from 'redux-tiles';
const uiTile = createSyncTile({
  type: ['ui', 'elements'],
  fn: ({ params }) =&gt; params,
  // type will be `notificationBar`
  nesting: ({ type }) =&gt; [type],
});
</code></pre>

<p>And that's it -- it will be update correctly on arbitrary nesting. Also, tile provides selectors, so you don't have to worry personally where precisely data is located, you can just use them.
So, I don't want to say it is the best solution, but the idea is pretty simple -- don't be afraid to write your own implementation, and then just use factory to solve this issue.</p>


blocks|key|276856|text|如果您正在使用Immutable.js，您可以在嵌套结构主题下面查看一些可能对您有帮助的函数，我个人使用mergeDeep|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|276857|prevState.mergeDeep({+userInfo:+{
++username:+action.payload.username,
}+}),|code-block|syntax|javascript|276858|entityMap|0|LINK|mutability|MUTABLE|url|https://facebook.github.io/immutable-js/^0|O|4|1G|9|7|C|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|D]]|E|@$9|Y|A|Z|1|10]]|F|$]]|$1|G|3|H|5|I|7|11|8|@]|E|@]|F|$J|K]]|$1|L|3|-4|5|6|7|12|8|@]|E|@]|F|$]]]|M|$N|$5|O|P|Q|F|$R|S]]]]

<p>If you're using <a href="https://facebook.github.io/immutable-js/" rel="nofollow noreferrer">Immutable.js</a>, you can look under <strong>Nested Structures</strong> topic some functions that may help you, I personally use <code>mergeDeep</code>:</p>

<pre><code>prevState.mergeDeep({ userInfo: {
  username: action.payload.username,
} }),
</code></pre>


<p>Sometimes reducers get kind of messy:</p>

<pre><code>const initialState = {
    notificationBar: {
        open: false,
    },
};

export default function (state = initialState, action) {
  switch (action.type) {
    case actions.LAYOUT_NOTIFICATIONBAR_OPEN:
      return Object.assign({}, state, {
        // TODO: Find a cleaner way to do this!
        notificationBar: Object.assign({}, state.notificationBar, {
          open: true,
        }),
      });
    default:
      return state;
  }
}
</code></pre>

<p>Is there a more terse way to do this?</p>


Cleaner/shorter way to update nested state in Redux?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

有时减速机会变得很乱：const initialState = {    notificationBar: {        open: false,    },};export default function (state = initialState, action) {  switch (action.type...

问更新Redux中嵌套状态的更简洁/更短的方法？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问更新Redux中嵌套状态的更简洁/更短的方法？EN