# RFC: Deprecating prosemirror-schema-table and attribute constraints in schemas

**URL:** <https://discuss.prosemirror.net/t/rfc-deprecating-prosemirror-schema-table-and-attribute-constraints-in-schemas/864>\
**Category:** Uncategorized\
**Created:** [July 6, 2017, 9:52am UTC](https://discuss.prosemirror.net/t/rfc-deprecating-prosemirror-schema-table-and-attribute-constraints-in-schemas/864 "2017-07-06T09:52:28Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [July 19, 2017, 7:39am UTC](https://discuss.prosemirror.net/t/rfc-deprecating-prosemirror-schema-table-and-attribute-constraints-in-schemas/864/6 "2017-07-19T07:39:01Z")

</div>

> [@bradleyayers](#):
>
> What ideas did you have for mitigating this problem?

My impression is that it is enough to simply know/document that a given constraint isn’t guaranteed to always be fulfilled, and write code that interacts with it defensively. For the table shape thing, that worked well so far.

---

_[View the full topic](https://discuss.prosemirror.net/t/rfc-deprecating-prosemirror-schema-table-and-attribute-constraints-in-schemas/864)._