# Why is NodeView.update called with different node types?

**URL:** <https://discuss.prosemirror.net/t/why-is-nodeview-update-called-with-different-node-types/4805>\
**Category:** Uncategorized\
**Created:** [August 7, 2022, 7:21pm UTC](https://discuss.prosemirror.net/t/why-is-nodeview-update-called-with-different-node-types/4805 "2022-08-07T19:21:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marijn](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/marijn/32/15_2.png) [@marijn](https://discuss.prosemirror.net/u/marijn)\
**Post date:** [August 7, 2022, 8:32pm UTC](https://discuss.prosemirror.net/t/why-is-nodeview-update-called-with-different-node-types/4805/2 "2022-08-07T20:32:48Z")

</div>

It is possible for a node view to support several types of nodes, and be able to update from one to another. But yeah, if I were to design the interface now I’d make that require an explicit opt-in, since despite the docs clearly mentioning this, it keeps tripping people up.

---

_[View the full topic](https://discuss.prosemirror.net/t/why-is-nodeview-update-called-with-different-node-types/4805)._